From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.rutgers.edu
Subject: pte_list-2.1.66
Date: Thu, 27 Nov 1997 03:04:18 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.971127024507.21730A-100000@as200.spellcast.com> (raw)
In-Reply-To: <Pine.LNX.3.91.971125222922.14082B-100000@mirkwood.dummy.home>
Hello all,
I updated my pte list patch against 2.1.66, and will be actively working
on it again. My short term goals include getting the [minimal] work done
needed to make it function on Alphas, and improving the kswapd heuristics
a lot more. It still probably breaks the shm stuff... Fetch from
http://www.kvack.org/~blah/patches/pte_list-2.1.66.diff.gz
Also, if people want to discuss mm ideas/developement heavily, I've
created a mailing list (submit to linux-mm@kvack.org, subscribe is
majordomo@kvack.org). It would be nice to see any rough little mm tweaks
people are hiding. ;)
-ben
prev parent reply other threads:[~1997-11-27 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.95.971125160146.13249B-100000@as200.spellcast.com>
1997-11-25 21:31 ` page->pte_head, Was:[URGENT ASSISTANCE REQUESTED] production , machines dying Rik van Riel
1997-11-27 8:04 ` Benjamin C.R. LaHaise [this message]
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.971127024507.21730A-100000@as200.spellcast.com \
--to=blah@kvack.org \
--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