[3851] in arla-drinkers
Re: is cache-only-prefixes an nnpfs limitation?
daemon@ATHENA.MIT.EDU (Tomas Olsson)
Tue Apr 4 06:40:11 2006
From arla-drinkers-bounces@stacken.kth.se Tue Apr 04 10:40:11 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 15917 invoked from network); 4 Apr 2006 10:40:11 -0000
Received: from mx3.kth.se (130.237.48.97)
by charon.mit.edu with SMTP; 4 Apr 2006 10:40:11 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx3.kth.se (Postfix) with ESMTP id C4EDD140C05;
Tue, 4 Apr 2006 12:40:09 +0200 (CEST)
Received: from mx3.kth.se ([127.0.0.1])
by localhost (mx3.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP
id 15147-01-8; Tue, 4 Apr 2006 12:40:07 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx3.kth.se (Postfix) with ESMTP id 3821E1406DC;
Tue, 4 Apr 2006 12:40:07 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 8D994534F3;
Tue, 4 Apr 2006 12:40:06 +0200 (CEST)
X-Original-To: arla-drinkers@tapas.stacken.kth.se
Delivered-To: arla-drinkers@tapas.stacken.kth.se
Received: from brev.stacken.kth.se (brev.stacken.kth.se [130.237.234.84])
by tapas.stacken.kth.se (Postfix) with ESMTP id 60B6A534F3
for <arla-drinkers@tapas.stacken.kth.se>;
Tue, 4 Apr 2006 12:40:04 +0200 (CEST)
Received: from mx1.kth.se (mx1.kth.se [130.237.32.140])
by brev.stacken.kth.se (8.12.10/8.12.10) with ESMTP id k34Ae3bB012844
for <arla-drinkers@stacken.kth.se>;
Tue, 4 Apr 2006 12:40:03 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 8FC80140898
for <arla-drinkers@stacken.kth.se>;
Tue, 4 Apr 2006 12:40:03 +0200 (CEST)
Received: from mx1.kth.se ([127.0.0.1])
by localhost (mx1.kth.se [127.0.0.1]) (amavisd-new,
port 10024) with LMTP
id 23755-01-23; Tue, 4 Apr 2006 12:40:01 +0200 (CEST)
Received: from kashyyyk.ite.kth.se (kashyyyk.ite.kth.se [130.237.31.35])
by mx1.kth.se (Postfix) with ESMTP id DEF0B1407A8;
Tue, 4 Apr 2006 12:40:01 +0200 (CEST)
Received: by kashyyyk.ite.kth.se (Postfix, from userid 18404)
id D5EF57C861C; Tue, 4 Apr 2006 12:40:01 +0200 (CEST)
From: Tomas Olsson <tol@stacken.kth.se>
To: Adam Megacz <megacz@cs.berkeley.edu>
Subject: Re: is cache-only-prefixes an nnpfs limitation?
References: <x3mzf1bugb.fsf@nowhere.com>
Date: 04 Apr 2006 12:40:01 +0200
In-Reply-To: <x3mzf1bugb.fsf@nowhere.com>
Message-ID: <lsrpsjxtyim.fsf@kashyyyk.ite.kth.se>
Lines: 27
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at kth.se
X-Spam-Status: No, hits=-4.9 tagged_above=-200.0 required=5.0 tests=BAYES_00
X-Spam-Level:
Cc: arla-drinkers@stacken.kth.se
X-BeenThere: arla-drinkers@stacken.kth.se
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: Arla discussions <arla-drinkers.stacken.kth.se>
List-Unsubscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=unsubscribe>
List-Archive: <http://lists.stacken.kth.se/pipermail/arla-drinkers>
List-Post: <mailto:arla-drinkers@stacken.kth.se>
List-Help: <mailto:arla-drinkers-request@stacken.kth.se?subject=help>
List-Subscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: arla-drinkers-bounces@stacken.kth.se
Errors-To: arla-drinkers-bounces@stacken.kth.se
X-Virus-Scanned: by amavisd-new at kth.se
Adam Megacz <megacz@cs.berkeley.edu> writes:
> I understand that, currently, Arla must retrieve bytes 0..n of a file
> in order to access byte n+1. Is this a limitation imposed by nnpfs,
> or simply the way arlad currently works?
>
It's a limitation imposed by nnpfs. You probably want to take a look at the
protocol (arla/nnpfs/include/nnpfs/nnpfs_message.h) and arla/doc/nnpfs.txt
(may need an update). If you're adventurous, take a look at the protocol
version in block_branch in CVS, too. It's not exactly final.
> Specifically, I'm wondering about the possibilities of writing other
> filesystems that run on top of nnpfs (including the Win32 nnpfs), and
> I wanted to know if this limitation would be inherited.
>
Yup, the nnpfs implementation and protocol does limit things. It will get
less limiting, but I don't see us implementing completely free byte range
fetching. Apart from that, it should work. We've mentioned a few other
projects that use xfs/nnpfs here before. I guess arlad is the most complete
reference on how it is supposed to work, but it's not a very clear design.
If you happen to write up a little libnnpfs or so, I'm _very_ interested.
AFAIK, w2k nnpfs works very well for demos and benchmarks, but it does have
threading issues. Needs some work to be fit for production use.
What do you have in mind?
/t
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
