[3966] in arla-drinkers
Re: is cache-only-prefixes an nnpfs limitation?
daemon@ATHENA.MIT.EDU (Tomas Olsson)
Wed Jun 21 05:55:40 2006
From arla-drinkers-bounces@stacken.kth.se Wed Jun 21 09:55:40 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 14114 invoked from network); 21 Jun 2006 09:55:40 -0000
Received: from mx1.kth.se (130.237.32.140)
by charon.mit.edu with SMTP; 21 Jun 2006 09:55:40 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 6A42A140719;
Wed, 21 Jun 2006 11:55:33 +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 20551-02-36; Wed, 21 Jun 2006 11:55:29 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx1.kth.se (Postfix) with ESMTP id AD0F9140F98;
Wed, 21 Jun 2006 11:55:27 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 17B4D534FC;
Wed, 21 Jun 2006 11:55:26 +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 55135534FC
for <arla-drinkers@tapas.stacken.kth.se>;
Wed, 21 Jun 2006 11:55:23 +0200 (CEST)
Received: from mx2.kth.se (mx2.kth.se [130.237.48.98])
by brev.stacken.kth.se (8.12.10/8.12.10) with ESMTP id k5L9tMAr012473
for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 11:55:22 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx2.kth.se (Postfix) with ESMTP id 7C9A51418CA
for <arla-drinkers@stacken.kth.se>;
Wed, 21 Jun 2006 11:55:22 +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 23924-01-74; Wed, 21 Jun 2006 11:55:19 +0200 (CEST)
Received: from kashyyyk.ite.kth.se (kashyyyk.ite.kth.se [130.237.31.35])
by mx2.kth.se (Postfix) with ESMTP id AE24D14187A;
Wed, 21 Jun 2006 11:55:19 +0200 (CEST)
Received: by kashyyyk.ite.kth.se (Postfix, from userid 18404)
id 57F71960127; Wed, 21 Jun 2006 11:55:18 +0200 (CEST)
From: Tomas Olsson <tol@stacken.kth.se>
To: Pavel Cahyna <pcah8322@artax.karlin.mff.cuni.cz>
Subject: Re: is cache-only-prefixes an nnpfs limitation?
References: <x3mzf1bugb.fsf@nowhere.com> <lsrpsjxtyim.fsf@kashyyyk.ite.kth.se>
<x33bgskjcm.fsf@nowhere.com> <lsrpsjwsbe8.fsf@kashyyyk.ite.kth.se>
<x38xqetym2.fsf@nowhere.com> <lsrfykmpliu.fsf@kashyyyk.ite.kth.se>
<20060621092106.GC12107@artax.karlin.mff.cuni.cz>
Date: 21 Jun 2006 11:55:16 +0200
In-Reply-To: <20060621092106.GC12107@artax.karlin.mff.cuni.cz>
Message-ID: <lsr7j3ag7ej.fsf@kashyyyk.ite.kth.se>
Lines: 16
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
Pavel Cahyna <pcah8322@artax.karlin.mff.cuni.cz> writes:
> sorry for replying to this old thread...
>
I don't mind, it's one of my favourites...
> 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.
>
Well, technically yes. And I would love it. The difficult part is the
requiement that we should be able to read/write files larger than the
cache. That means cache eviction of parts of files, and making new holes
in files doesn't seem to be widely supported yet. Convince me :)
/t
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
