[3860] in arla-drinkers

home help back first fref pref prev next nref lref last post

Re: is cache-only-prefixes an nnpfs limitation?

daemon@ATHENA.MIT.EDU (Adam Megacz)
Tue Apr 4 19:32:24 2006

From arla-drinkers-bounces@stacken.kth.se Tue Apr 04 23:32:24 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 23157 invoked from network); 4 Apr 2006 23:32:24 -0000
Received: from mx2.kth.se (130.237.48.98)
  by charon.mit.edu with SMTP; 4 Apr 2006 23:32:24 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx2.kth.se (Postfix) with ESMTP id 20894140ACB;
	Wed,  5 Apr 2006 01:32:23 +0200 (CEST)
Received: from mx2.kth.se ([127.0.0.1])
 by localhost (mx2.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP
 id 17623-02-2; Wed,  5 Apr 2006 01:32:20 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
	by mx2.kth.se (Postfix) with ESMTP id 96F58140AE4;
	Wed,  5 Apr 2006 01:32:14 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
	by tapas.stacken.kth.se (Postfix) with ESMTP id 1351C534F3;
	Wed,  5 Apr 2006 01:32:10 +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 D82CE534F3
	for <arla-drinkers@tapas.stacken.kth.se>;
	Wed,  5 Apr 2006 01:32:05 +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 k34NW5bB021581
	for <arla-drinkers@stacken.kth.se>;
	Wed, 5 Apr 2006 01:32:05 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx1.kth.se (Postfix) with ESMTP id 03347140833
	for <arla-drinkers@stacken.kth.se>;
	Wed,  5 Apr 2006 01:32:04 +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 07012-06-18 for <arla-drinkers@stacken.kth.se>;
	Wed,  5 Apr 2006 01:32:03 +0200 (CEST)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
	by mx1.kth.se (Postfix) with ESMTP id CEF5914072C
	for <arla-drinkers@stacken.kth.se>;
	Wed,  5 Apr 2006 01:32:03 +0200 (CEST)
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1FQv0A-0006bJ-7t
	for arla-drinkers@stacken.kth.se; Wed, 05 Apr 2006 01:31:58 +0200
Received: from megacz.com ([216.237.119.186])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <arla-drinkers@stacken.kth.se>; Wed, 05 Apr 2006 01:31:58 +0200
Received: from megacz by megacz.com with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <arla-drinkers@stacken.kth.se>; Wed, 05 Apr 2006 01:31:58 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: arla-drinkers@stacken.kth.se
From: Adam Megacz <megacz@cs.berkeley.edu>
Subject: Re: is cache-only-prefixes an nnpfs limitation?
Date: Tue, 04 Apr 2006 16:32:25 -0700
Organization: Myself
Lines: 32
Message-ID: <x33bgskjcm.fsf@nowhere.com>
References: <x3mzf1bugb.fsf@nowhere.com> <lsrpsjxtyim.fsf@kashyyyk.ite.kth.se>
Mime-Version: 1.0
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: megacz.com
X-Home-Page: http://www.megacz.com/
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux)
Cancel-Lock: sha1:OGcLrR3UATME/PWiTFFZPl4trsU=
X-Virus-Scanned: by amavisd-new at kth.se
X-Spam-Status: No, hits=-3.4 tagged_above=-200.0 required=5.0 tests=BAYES_00, 
	RCVD_IN_BL_SPAMCOP_NET
X-Spam-Level: 
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


Tomas Olsson <tol@stacken.kth.se> writes:
> 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.

Well, as long as it's eventually moving towards the point where it can
fetch arbitrary blocks with some reasonably small blocksize, that's
probably good enough.

> 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.

Are there likely to be any data corruption, crashes, or hangs (due
solely to nnpfs)?  Or merely performance issues?

> If you happen to write up a little libnnpfs or so, I'm _very_ interested.

Would you throw rotten vegetables at me if it happened to appear in
the form of a native interface for Java code?  Perhaps I shouldn't
have mentioned this. ;)

> What do you have in mind?

Something sort of like a cross between coda and sfs, but with a heavy
emphasis on simplicity over performance.  And the ability to tunnel
over HTTP and DNS as last resorts.

  - a

-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380

_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers

home help back first fref pref prev next nref lref last post