[3967] in arla-drinkers
Re: is cache-only-prefixes an nnpfs limitation?
daemon@ATHENA.MIT.EDU (Harald Barth)
Wed Jun 21 10:06:14 2006
From arla-drinkers-bounces@stacken.kth.se Wed Jun 21 14:06:14 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 25375 invoked from network); 21 Jun 2006 14:06:14 -0000
Received: from mx2.kth.se (130.237.48.98)
by charon.mit.edu with SMTP; 21 Jun 2006 14:06:14 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx2.kth.se (Postfix) with ESMTP id 1A2F71427AF;
Wed, 21 Jun 2006 16:06:13 +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 21172-01-33; Wed, 21 Jun 2006 16:06:11 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx2.kth.se (Postfix) with ESMTP id A26CD141F04;
Wed, 21 Jun 2006 16:06:11 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 11EEB534FC;
Wed, 21 Jun 2006 16:06:11 +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 8D0C4534FC
for <arla-drinkers@tapas.stacken.kth.se>;
Wed, 21 Jun 2006 16:06:09 +0200 (CEST)
Received: from mx3.kth.se (mx3.kth.se [130.237.48.97])
by brev.stacken.kth.se (8.12.10/8.12.10) with ESMTP id k5LE67Ar014406
for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 16:06:08 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx3.kth.se (Postfix) with ESMTP id 9DC3214101D
for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 16:06:07 +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 09258-01-32 for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 16:06:06 +0200 (CEST)
Received: from habarber.pdc.kth.se (unknown
[IPv6:2001:6b0:1:1dd0:203:47ff:fe8c:b968])
by mx3.kth.se (Postfix) with ESMTP id 7727B140879
for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 16:06:06 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by habarber.pdc.kth.se (8.13.3/8.13.3) with ESMTP id k5LE66s2012636
for <arla-drinkers@stacken.kth.se>; Wed, 21 Jun 2006 16:06:06 +0200
Date: Wed, 21 Jun 2006 16:05:51 +0200 (MEST)
Message-Id: <20060621.160551.41635819.haba@habarber.pdc.kth.se>
To: arla-drinkers@stacken.kth.se
Subject: Re: is cache-only-prefixes an nnpfs limitation?
From: Harald Barth <haba@pdc.kth.se>
In-Reply-To: <lsr7j3ag7ej.fsf@kashyyyk.ite.kth.se>
References: <lsrfykmpliu.fsf@kashyyyk.ite.kth.se>
<20060621092106.GC12107@artax.karlin.mff.cuni.cz>
<lsr7j3ag7ej.fsf@kashyyyk.ite.kth.se>
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:
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
> > I have an idea, could the 1:1 mapping stay, with the cache file becoming a
> > "sparse file"? The "holes" would fill the part of the cache file that
> > does not contain valid data.
This would mean that your cache file system or cache memory must support 64-bit
addressing. I would not like that requirement.
> That means cache eviction of parts of files, and making new holes
> in files doesn't seem to be widely supported yet.
Yes. When reading a big file, it must be possible to throw away the
beginning or middle to be able to fit the end in the cache.
Harald.
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
