From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Whitehouse <steve@gw.chygwyn.com>
Subject: Re: File perforation.
Date: Wed, 8 Jan 2003 23:36:35 +0000 (GMT)
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <200301082336.XAA16402@gw.chygwyn.com>
References: <23614.1042067811@passion.cambridge.redhat.com>
Reply-To: Steve Whitehouse <Steve@ChyGwyn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
To: dwmw2@infradead.org (David Woodhouse)
In-Reply-To: <23614.1042067811@passion.cambridge.redhat.com> from "David Woodhouse" at Jan 08, 2003 11:16:51 PM
List-Id: linux-fsdevel.vger.kernel.org

Hi,

> 
> 
> steve@gw.chygwyn.com said:
> > So presumably a suitable advice value FADV_CLEAR (for example) could
> > be  used as an addition to the POSIX values ? 
> 
> Nothing else that fadvise() offers actually changes the file. They're all 
> optional -- if the kernel ignores your fadvise() call you can't even prove 
> that it's done so. I'm not sure it's a good fit.
>
Yes, I share your misgivings there. Perhaps keeping the interface idea but
giving it a different name. iadvise (for inode-advise) maybe ?

Steve.