From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Aucoin <Aucoin@Houston.RR.com>,
'Nick Piggin' <nickpiggin@yahoo.com.au>,
'Tim Schmielau' <tim@physik3.uni-rostock.de>,
clameter@sgi.com,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: la la la la ... swappiness
Date: Tue, 5 Dec 2006 08:59:14 -0800 [thread overview]
Message-ID: <20061205085914.b8f7f48d.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612050754020.3542@woody.osdl.org>
On Tue, 5 Dec 2006 08:17:51 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Tue, 5 Dec 2006, Aucoin wrote:
> >
> > > Louis, exactly how do you allocate that big 1.6GB shared area?
> >
> > Ummm, shm_open, ftruncate, mmap ? Is it a trick question ? The process
> > responsible for initially setting up the shared area doesn't stay resident.
>
> Not a trick question, I just suddenly realized that I really should have
> expected the SHM pages to show up in the LRU lists (either inactive or
> active) and shown up as "cached" pages too. Afaik, the SHM routines all
> end up using the page cache and the LRU for the backing store.
>
> But your 1.6GB thing doesn't show up anywhere.
>
> (I'm sure it's intentional, and I've just forgotten some detail. We
> probably remove pages from the LRU lists when they are locked. Anyway, my
> original point was that since the pages _aren't_ on the LRU lists, the VM
> really should basically act as if they didn't exist at all, but there are
> probably things that still base their decisions on the _total_ amount of
> memory)
>
Yes, those pages should be on the LRU. I suspect they never got paged in
or something. But that would mean they weren't mlocked. Is a mystery.
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-12-05 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612050641.kB56f7wY018196@ms-smtp-06.texas.rr.com>
2006-12-05 16:17 ` Linus Torvalds
2006-12-05 16:59 ` Andrew Morton [this message]
2006-12-05 17:41 ` aucoin, Andrew Morton
2006-12-05 18:31 ` Christoph Lameter
2006-12-05 18:44 ` Linus Torvalds
2006-12-05 19:32 ` Christoph Lameter
2006-12-05 20:02 ` Andrew Morton
2006-12-05 20:15 ` Christoph Lameter
2006-12-05 20:48 ` Andrew Morton
2006-12-05 20:59 ` Christoph Lameter
2006-12-05 21:39 ` Andrew Morton
2006-12-05 23:20 ` Christoph Lameter
2006-12-12 15:12 ` Aucoin
2006-12-05 20:52 ` Andrew Morton
2006-12-05 20:39 ` aucoin, Linus Torvalds
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=20061205085914.b8f7f48d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Aucoin@Houston.RR.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@osdl.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