[3874] in arla-drinkers
Re: is cache-only-prefixes an nnpfs limitation?
daemon@ATHENA.MIT.EDU (Harald Barth)
Mon Apr 10 02:38:41 2006
From arla-drinkers-bounces@stacken.kth.se Mon Apr 10 06:38:41 2006
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 4750 invoked from network); 10 Apr 2006 06:38:40 -0000
Received: from mx2.kth.se (130.237.48.98)
by charon.mit.edu with SMTP; 10 Apr 2006 06:38:40 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx2.kth.se (Postfix) with ESMTP id C0344140A6B;
Mon, 10 Apr 2006 08:38:39 +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 07358-01-70; Mon, 10 Apr 2006 08:38:38 +0200 (CEST)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx2.kth.se (Postfix) with ESMTP id DA9FF140A82;
Mon, 10 Apr 2006 08:38:37 +0200 (CEST)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 9F17D534F3;
Mon, 10 Apr 2006 08:38:37 +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 1285F534F3
for <arla-drinkers@tapas.stacken.kth.se>;
Mon, 10 Apr 2006 08:38:34 +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 k3A6cYla004816;
Mon, 10 Apr 2006 08:38:34 +0200 (MET DST)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 12ABF140A9D;
Mon, 10 Apr 2006 08:38:34 +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 30664-02-80; Mon, 10 Apr 2006 08:38:32 +0200 (CEST)
Received: from habarber.pdc.kth.se (habitude.stacken.kth.se [130.237.237.21])
by mx1.kth.se (Postfix) with ESMTP id 71863140AB9;
Mon, 10 Apr 2006 08:38:32 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
by habarber.pdc.kth.se (8.13.3/8.13.3) with ESMTP id k3A6cZRR031833;
Mon, 10 Apr 2006 08:38:35 +0200
Date: Mon, 10 Apr 2006 08:38:35 +0200 (MEST)
Message-Id: <20060410.083835.35511037.haba@habarber.pdc.kth.se>
To: tol@stacken.kth.se
Subject: Re: is cache-only-prefixes an nnpfs limitation?
From: Harald Barth <haba@pdc.kth.se>
In-Reply-To: <lsrfykmpliu.fsf@kashyyyk.ite.kth.se>
References: <lsrpsjwsbe8.fsf@kashyyyk.ite.kth.se> <x38xqetym2.fsf@nowhere.com>
<lsrfykmpliu.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:
Cc: megacz@cs.berkeley.edu, 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
> The HPC folks are almost ready to kill for this (and cacheless writes).
> Right now they'll have to resort to linking against arlad to do it.
Oh, yes we will ;-) The reason is that our users very often read small
files (the "application") often and big files (the "data") once. Then
they write big files (the "result") once. This behaviour is very
differet from for example a class of students who read and write small
files (the "program") often and read big files (the "compiler") often
and almost never write big files. Some time in the future I hope we
can hint the cache what to do. If the HPC folks would write stuff in C
I could tell them to open(2) with O_DIRECT and then implement some
other cache strategy for that, but most of these applictions are "behind"
FORTRAN I/O.
> BTW, what's the current status on ways for the user to communicate such
> hints to the fs on various OS:es? I just love Windows in this respect,
> they have tons of flags. They even have FILE_OPEN_FOR_FREE_SPACE_QUERY. I
> wonder if it's ever used.
In libc we could use open(2) with O_DIRECT, I just do not know it it
would help my FORTRAN HPC folks. The C and C++ HPC folks could probably
be teached to use O_DIRECT but I suspect that some other means (like
an environment variable) might be necessary.
Hm. I don't know what happens if I use O_DIRECT in Arla today if it is
ignored or passed down on the cache file open.
Harald.
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
