From: Chuck Lever <cel@monkey.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mincore for i386, against 2.3.51
Date: Mon, 13 Mar 2000 14:56:32 -0500 (EST) [thread overview]
Message-ID: <Pine.BSO.4.10.10003131438050.12643-100000@funky.monkey.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10003131032290.1257-100000@penguin.transmeta.com>
On Mon, 13 Mar 2000, Linus Torvalds wrote:
> I think that "incore" should be a generic VM function, and be based solely
> on the VMA and the associated address space.
at one point i tried just walking the page tables, but that really didn't
give the results i wanted -- every page appeared to be "in core".
> So I'd prefer something that does not have the "incore" function at all,
> and if that convinces somebody else to change shm to use the address_space
> stuff to get a working mincore(), all the better. Ok?
hmm. i created the "incore" method because mincore needs to synchronize
with the swapping method used for each of the different vma types. this
is different for shm's vs. mapped files -- they both use locking methods
that are independent of one another. any ideas about how to get around
this without using an "incore" vm_op? do you think grabbing the mm
semaphor is enough?
i also wanted to check the page_uptodate bit for mapped files, but this
doesn't make sense for shm, for example. i think the semantics of "page
is in memory" can be different enough for the different types of vmas that
having a separate hook for each is necessary.
btw i think i've ended up in your kill file. direct mail i send to you
appears to be lost.
- Chuck Lever
--
corporate: <chuckl@netscape.com>
personal: <chucklever@netscape.net> or <cel@monkey.org>
The Linux Scalability project:
http://www.citi.umich.edu/projects/linux-scalability/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-03-13 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 0:45 Chuck Lever
2000-03-13 17:46 ` Kanoj Sarcar
2000-03-13 18:16 ` Chuck Lever
2000-03-13 18:28 ` Kanoj Sarcar
2000-03-13 18:35 ` Linus Torvalds
2000-03-13 19:56 ` Chuck Lever [this message]
2000-03-13 20:31 ` Linus Torvalds
2000-03-13 21:32 ` Chuck Lever
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.BSO.4.10.10003131438050.12643-100000@funky.monkey.org \
--to=cel@monkey.org \
--cc=linux-mm@kvack.org \
--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