From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: Rik van Riel <H.H.vanRiel@fys.ruu.nl>,
Linus Torvalds <torvalds@transmeta.com>,
Itai Nahshon <nahshon@actcom.co.il>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
paubert@iram.es, linux-kernel@vger.rutgers.edu,
Ingo Molnar <mingo@chiara.csoma.elte.hu>,
linux-mm@kvack.org
Subject: Re: How to read-protect a vm_area?
Date: Fri, 20 Feb 1998 00:41:19 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.980220001508.8311A-100000@as200.spellcast.com> (raw)
In-Reply-To: <199802192321.XAA06580@dax.dcs.ed.ac.uk>
On Thu, 19 Feb 1998, Stephen C. Tweedie wrote:
...
> Please do let me know if you want to start hacking around with this
> code --- we probably want to coordinate with some of the other VM
> things happening at the moment (in particular, things like Ingo's swap
> prediction and the dirty page caching suggestions).
...
Just to let people know, as a successor to my pte-list/swapping patch from
the 2.1.48/66 days (which made running X on my nfs-root'd [34]86
possible/reliable), I'm currently mostly done a patch that does Mach-style
page replacement (active/inactive/free) as an alternative to kswapd. I'm
also hoping to work on adding a per-cpu free page cache to get_free_page
later this month when my PPros arrive (grumble).
As Rik mentioned, please feel free to make use of linux-mm@kvack.org for
discussion purposes. (echo subscribe | mail majordomo@kvack.org) It's
been quite, but then it's Febuary.
About the dirty page caching suggestions: Eric W. Biederman
<ebiederm+eric@npwt.net> wrote patches to support that against 2.1.78, but
last time the issue was brought up, things became messy as NFS needs
dentries now, yet we'll only ever have inodes in struct page. Now that
the dentry list is back in the inode, perhaps a patch to revert
read/writepage to non-dentry arguments could be accepted? (NFS could get
its dentry from the i_dentry list.)
Linus: how far off are you hoping for 2.2? It seems like there are
icebreakers out on the first code freeze... Or maybe that just how things
work ;-)
-ben
next parent reply other threads:[~1998-02-20 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802192321.XAA06580@dax.dcs.ed.ac.uk>
1998-02-20 5:41 ` Benjamin C.R. LaHaise [this message]
1998-02-23 23:17 ` PATCH: Swap shared pages (was: How to read-protect a vm_area?) Stephen C. Tweedie
1998-02-23 23:27 ` Linus Torvalds
1998-02-24 0:08 ` Benjamin C.R. LaHaise
1998-02-24 9:45 ` Stephen C. Tweedie
1998-02-24 9:42 ` Rik van Riel
1998-02-24 23:38 ` Stephen C. Tweedie
1998-02-25 10:41 ` Rik van Riel
1998-02-25 19:00 ` Stephen C. Tweedie
1998-02-25 22:05 ` Rik van Riel
1998-02-24 11:16 ` Thomas Sailer
[not found] ` <Pine.LNX.3.96.980224152231.7112A-100000@renass3.u-strasbg.fr>
1998-02-24 23:38 ` Stephen C. Tweedie
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=Pine.LNX.3.95.980220001508.8311A-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=H.H.vanRiel@fys.ruu.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=nahshon@actcom.co.il \
--cc=paubert@iram.es \
--cc=sct@dcs.ed.ac.uk \
--cc=torvalds@transmeta.com \
/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