From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: VGER kernel list <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org, Chuck Lever <cel@monkey.org>
Subject: Re: posix_fadvise
Date: Fri, 14 Apr 2000 22:45:52 +0200 [thread overview]
Message-ID: <20000414224552.A30555@pcep-jamie.cern.ch> (raw)
In-Reply-To: <m3snwofzo4.fsf@localhost.localnet>; from Ulrich Drepper on Fri, Apr 14, 2000 at 08:52:11AM -0700
Ulrich Drepper wrote:
> > What does POSIX_FADV_DONTNEED mean? MADV_DONTNEED has at least three
> > incompatible meanings between different unix systems...
>
> Their definition is:
>
> Specifies that the applicatione xpects that it will not access the
> specified data in the near future.
Ok. You should be aware that the present Linux implementation of
MADV_DONTNEED is "nukes dirty data". Do you have a POSIX standard that
says POSIX MADV_DONTNEED should be similar to POSIX_FADV_DONTNEED?
There was some discussion on linux-mm about renaming this behaviour to
MADV_WONTNEED or MADV_DISCARD to avoid ambiguity. Some other OSes
implement MADV_DONTNEED by discarding data, but there are at least two
other semantics around including one like POSIX_FADV_DONTNEED.
enjoy,
-- Jamie
--
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 parent reply other threads:[~2000-04-14 20:45 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 ` Jamie Lokier [this message]
2000-04-14 20:56 ` posix_fadvise Ulrich Drepper
2000-04-14 21:24 ` posix_fadvise Jamie Lokier
2000-04-14 21:35 ` posix_fadvise Ulrich Drepper
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=20000414224552.A30555@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=cel@monkey.org \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox