[3873] in arla-drinkers
Re: is cache-only-prefixes an nnpfs limitation?
daemon@ATHENA.MIT.EDU (Harald Barth)
Mon Apr 10 01:49:01 2006
From arla-drinkers-bounces@stacken.kth.se Mon Apr 10 05:49:01 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 2504 invoked from network); 10 Apr 2006 05:49:01 -0000
Received: from mx1.kth.se (130.237.32.140)
by charon.mit.edu with SMTP; 10 Apr 2006 05:49:01 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 0CEF514093C;
Mon, 10 Apr 2006 07:49:00 +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 27737-01-44; Mon, 10 Apr 2006 07:48:58 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx1.kth.se (Postfix) with ESMTP id 6138614082B;
Mon, 10 Apr 2006 07:48:58 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 23E28534F3;
Mon, 10 Apr 2006 07:48:58 +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 A289D534F3
for <arla-drinkers@tapas.stacken.kth.se>;
Mon, 10 Apr 2006 07:48:56 +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 k3A5mula004390
for <arla-drinkers@stacken.kth.se>;
Mon, 10 Apr 2006 07:48:56 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id D1CE714093C
for <arla-drinkers@stacken.kth.se>;
Mon, 10 Apr 2006 07:48:55 +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 27737-01-43 for <arla-drinkers@stacken.kth.se>;
Mon, 10 Apr 2006 07:48:54 +0200 (CEST)
Received: from habarber.pdc.kth.se (habitude.stacken.kth.se [130.237.237.21])
by mx1.kth.se (Postfix) with ESMTP id 6DCF114082B
for <arla-drinkers@stacken.kth.se>;
Mon, 10 Apr 2006 07:48:54 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by habarber.pdc.kth.se (8.13.3/8.13.3) with ESMTP id k3A5mj46031764;
Mon, 10 Apr 2006 07:48:45 +0200
Date: Mon, 10 Apr 2006 07:48:44 +0200 (MEST)
Message-Id: <20060410.074844.52173074.haba@habarber.pdc.kth.se>
To: megacz@cs.berkeley.edu
Subject: Re: is cache-only-prefixes an nnpfs limitation?
From: Harald Barth <haba@pdc.kth.se>
In-Reply-To: <x38xqetym2.fsf@nowhere.com>
References: <x33bgskjcm.fsf@nowhere.com> <lsrpsjwsbe8.fsf@kashyyyk.ite.kth.se>
<x38xqetym2.fsf@nowhere.com>
X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
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
> "There is just one reson that one should have blockcache. You want
> to edit filer larger then you blockcache"
>
> Actually, I'm most interested in block caching for a different reason
> -- I often store large media files in AFS and seek around in them (ie
> access starting at random locations in the file). Many of these files
> would fit in my disk cache, but moving the entire file over the
> network or crowding (almost) everything else out of my local cache
> would be bad.
Correct, users sometimes want to do other operations than to start
reading from the beginning, but a block cache is not needed just for
the feature "random read". For example there could be a file with
holes which would be filled when needed. Files bigger than the cache
happen sometimes (not often though), but for these rare cases block
caching is needed.
I think Tomas answered all the other questions.
Harald.
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
