From: Linus Torvalds <torvalds@transmeta.com>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
Rik van Riel <H.H.vanRiel@fys.ruu.nl>,
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: PATCH: Swap shared pages (was: How to read-protect a vm_area?)
Date: Mon, 23 Feb 1998 15:27:13 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.3.95.980223152519.418B-100000@penguin.transmeta.com> (raw)
In-Reply-To: <199802232317.XAA06136@dax.dcs.ed.ac.uk>
On Mon, 23 Feb 1998, Stephen C. Tweedie wrote:
>
> The patch below, against 2.1.88, adds a bunch of new functionality to
> the swapper. The main changes are:
Ok, this looks clean, I've applied it to my current sources and pending no
surprises it will be in 89.
[ I've also changed the way we consider us to need more memory in kswapd,
but that was entirely orthogonal and did not impact these patches. ]
Knock wood,
Linus
next prev parent reply other threads:[~1998-02-23 23:27 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 ` How to read-protect a vm_area? Benjamin C.R. LaHaise
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 [this message]
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.980223152519.418B-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=H.H.vanRiel@fys.ruu.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=blah@kvack.org \
--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 \
/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