From: Ulrich Drepper <drepper@redhat.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: VGER kernel list <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org, Chuck Lever <cel@monkey.org>
Subject: Re: posix_fadvise
Date: 14 Apr 2000 14:35:25 -0700 [thread overview]
Message-ID: <m3aeiwcqn6.fsf@localhost.localnet> (raw)
In-Reply-To: Jamie Lokier's message of "Fri, 14 Apr 2000 23:24:30 +0200"
Jamie Lokier <lk@tantalophile.demon.co.uk> writes:
> You gave the definition as "the application does not need the data in
> the near future". If it were ok to nuke the data, the definition would
> say "the application does not need the data".
THere is no problem because the OS will recover. I don't say it's an
optimal implementation but given that the name is used differently on
different OSes (at least the one without the POSIX_ prefix) people
will have to adjust themselves.
Of course I would prefer if the option in the Linux kernel could do
what POSIX says and simply add a new option for the current behaviour.
But nobody listens to me anyway so why bother.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-14 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m38zyhgn2a.fsf@localhost.localnet>
[not found] ` <20000414105811.B29138@pcep-jamie.cern.ch>
[not found] ` <m3snwofzo4.fsf@localhost.localnet>
2000-04-14 20:45 ` posix_fadvise Jamie Lokier
2000-04-14 20:56 ` posix_fadvise Ulrich Drepper
2000-04-14 21:24 ` posix_fadvise Jamie Lokier
2000-04-14 21:35 ` Ulrich Drepper [this message]
2000-04-14 21:56 ` posix_fadvise Stephen C. Tweedie
2000-04-15 2:49 ` posix_fadvise Ulrich Drepper
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=m3aeiwcqn6.fsf@localhost.localnet \
--to=drepper@redhat.com \
--cc=cel@monkey.org \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lk@tantalophile.demon.co.uk \
/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.