From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.8.1-np1
Date: Fri, 20 Aug 2004 18:27:45 +1000 [thread overview]
Message-ID: <4125B601.5020303@yahoo.com.au> (raw)
http://www.kerneltrap.org/~npiggin/2.6.8.1-np1/
Again, this is only against 2.6.8.1-mm2 for now due to the amount of
scheduler and memory management patches in Andrew's tree.
This introduces per-zone inode and dcache scanning lists. These
introduce a theoretical problem (solveable, but would take some work)
however in practice I don't think it would cause a problem.
Also introduces "free_local_harder", which attempts to free some node
local memory before going remote. It is quite dumb at the moment, and
performs the scanning from process context (should be moved to kswapd
context), however it seems to usually do what it is supposed to. It
can be switched off by echo 0 > /proc/sys/vm/free_local_harder.
These should be good for NUMA performance, although free_local_harder
will, by definition, introduce regressions for some workloads.
Unfortunately, free_local_harder sits pretty firmly on top of my other
memory management changes, which may introduce problems themselves.
Even so, feedback would be cool.
reply other threads:[~2004-08-20 8:28 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=4125B601.5020303@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.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 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.