From: Steven Whitehouse <steve@gw.chygwyn.com>
To: dwmw2@infradead.org (David Woodhouse)
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: File perforation.
Date: Wed, 8 Jan 2003 23:36:35 +0000 (GMT) [thread overview]
Message-ID: <200301082336.XAA16402@gw.chygwyn.com> (raw)
In-Reply-To: <23614.1042067811@passion.cambridge.redhat.com> from "David Woodhouse" at Jan 08, 2003 11:16:51 PM
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.
next prev parent reply other threads:[~2003-01-08 23:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 22:06 File perforation David Woodhouse
2003-01-08 22:28 ` Eli Carter
2003-01-08 22:34 ` David Woodhouse
2003-01-08 22:56 ` Eli Carter
2003-01-08 23:14 ` David Woodhouse
2003-01-09 1:22 ` Andrew Morton
2003-01-09 3:23 ` Andreas Dilger
2003-01-08 23:17 ` Steven Whitehouse
2003-01-08 23:16 ` David Woodhouse
2003-01-08 23:36 ` Steven Whitehouse [this message]
2003-01-08 23:25 ` David Woodhouse
2003-01-10 1:39 ` Bryan Henderson
2003-01-08 22:45 ` Dave Kleikamp
2003-01-08 22:55 ` Matthew Wilcox
2003-01-08 23:02 ` David Woodhouse
2003-01-11 9:47 ` Christoph Hellwig
2003-01-10 1:34 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 22:24 Steven French
2003-01-11 1:46 ` Bryan Henderson
2003-01-13 3:52 Steven French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200301082336.XAA16402@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.