From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 2/2] perzone slab LRUs
Date: Thu, 29 Jul 2004 11:55:10 +1000 [thread overview]
Message-ID: <410858FE.3090007@yahoo.com.au> (raw)
In-Reply-To: <34870000.1091025443@[10.10.2.4]>
Martin J. Bligh wrote:
>>Oops, forgot to CC linux-mm.
>>
>>Nick Piggin wrote:
>>
>>>This patch is only intended for comments.
>>>
>>>This implements (crappy?) infrastructure for per-zone slab LRUs for
>>>reclaimable slabs, and moves dcache.c over to use that.
>>>
>>>The global unused list is retained to reduce intrusiveness, and another
>>>per-zone LRU list is added (which are still protected with the global
>>>dcache
>>>lock). This is an attempt to make slab scanning more robust on highmem and
>>>NUMA systems.
>>>
>
>Do we have slab that goes in highmem anywhere? I thought not .... 64 bit
>NUMA makes a lot of sense though.
>
>
I don't think so, but it still (I think) allows a general slab pressure
forumula
for highmem and muliple ZONE_NORMAL NUMA that doesn't blow up like our
current
one can.
The per-zone lists I'd say would have to help somewhat on the
performance side of
things as far as not taking remote cache misses during scanning. It
should also
mean that a low memory node will not globally shrink masses of slab from
nodes that
have plenty of memory.
As far as the dependant inodes problem goes - it could be a significant
problem,
and I think would need to be solved before perzone slab LRUs are a
viable option.
The most simplistic way I can see to solve it is: if we scan an inode
that is pinned
by dentries, scan its pinning dentries instead.
--
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:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-07-29 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <410789EB.1060209@yahoo.com.au>
2004-07-28 11:13 ` [RFC][PATCH 2/2] perzone slab LRUs Nick Piggin
2004-07-28 14:37 ` Martin J. Bligh
2004-07-29 1:55 ` Nick Piggin [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=410858FE.3090007@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.