From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Robert Love <rml@novell.com>, Andy Isaacson <adi@hexapodia.org>,
linux-kernel@vger.kernel.org
Subject: Re: wrong madvise(MADV_DONTNEED) semantic
Date: Tue, 28 Jun 2005 22:30:57 +0200 [thread overview]
Message-ID: <20050628203057.GD4453@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20050628202053.GO4645@bouh.labri.fr>
On Tue, 28 June 2005 22:20:53 +0200, Samuel Thibault wrote:
> Jörn Engel, le Tue 28 Jun 2005 22:17:04 +0200, a écrit :
> > If the application knows 100% that it is the _only_ possible user of
> > this data and will never again use it, dropping dirty pages might be a
> > sane option. Effectively that translates to anonymous memory only.
>
> And private file mappings?
As in inode->i_nlink == 0? Yes, if you can prove that only this one
thread still has it open. How to deal with multithreaded processes?
I don't know and would default to "write it back" again.
Besides, writing the dirty pages to backing store can only hurt
performance, never correctness. The data could already be synced at
the time of the madvice call anyway.
Jörn
--
This above all: to thine own self be true.
-- Shakespeare
next prev parent reply other threads:[~2005-06-28 20:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 13:43 Samuel Thibault
2005-06-28 14:38 ` [Patch] Hotfix for " Jörn Engel
2005-06-28 18:16 ` Andy Isaacson
2005-06-28 18:28 ` Robert Love
2005-06-28 18:53 ` Andy Isaacson
2005-06-28 19:23 ` Robert Love
2005-06-28 19:41 ` Samuel Thibault
2005-06-28 20:03 ` Jörn Engel
2005-06-28 20:05 ` Robert Love
2005-06-28 20:17 ` Jörn Engel
2005-06-28 20:20 ` Samuel Thibault
2005-06-28 20:30 ` Jörn Engel [this message]
2005-06-28 20:37 ` Andy Isaacson
2005-07-05 23:39 ` Darren Hart
2005-06-29 16:53 ` wrong madvise(MADV DONTNEED) semantic Michael Kerrisk
2005-06-29 17:22 ` Jamie Lokier
2005-06-29 16:34 ` Michael Kerrisk
2005-06-28 18:54 ` wrong madvise(MADV_DONTNEED) semantic Samuel Thibault
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=20050628203057.GD4453@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=adi@hexapodia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=samuel.thibault@ens-lyon.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
all inboxes | Powered by JetHome®