From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
Cc: linux-mm@kvack.org
Subject: reverse pte mapping update
Date: Mon, 9 Mar 1998 13:58:48 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.980309130055.8617C-100000@kanga.kvack.org> (raw)
Hello Stephen et all,
Just a quick update to say that I've got something that's half-working,
and given a few days more work it'll be worth testing. At least it boots
and allows me to compile the next change.
On another note, I'm becoming concerned about the manipulations being done
to vmas belonging to other mm's now - mostly that we'll be wanting to
manipulate them much more frequently than at present. Stephen, if you
could give me a hint about what direction you're going with your page
cache locking patch, it will help me start putting together a picture of
we'll fit everything together.
Along the same line of thought, I'm wondering if we can dispense of
mm->mmap_sem for most cases? I remember hearing that glibc will soon have
an async-io implementation, and I believe clone with shared vm is going to
be the basis for the implementation. This will also effect a future
threaded version of apache, which will use mmap'd files across several
threads being thrown at sockets to avoid the extra copies. Eliminating
the lock probably isn't possible, but changing it to a read-write blocking
lock is probably the easiest. The kernel should have such a generic
primative anyways.
Linux-mm people: is anyone interested in putting together a test suite to
excercise various aspects of the mm code? Ideally I'd like to see us put
together a large enough test suite to run a complete coverage test on the
kernel code. Given that this is a pretty big task, it will take a while.
Perhaps running the kernel under an emulator (say 68k/Amiga as UAE is
pretty complete, barring the MMU [easy]), or using the MkLinux port
would help in creating a more useful testing environment.
-ben
reply other threads:[~1998-03-09 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.980309130055.8617C-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=linux-mm@kvack.org \
--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