From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Robin Holt <holt@sgi.com>, akpm@osdl.org
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: ia64 needs to shake memory from quicklists when there is memory pressure.
Date: Wed, 09 Mar 2005 09:15:10 -0800 [thread overview]
Message-ID: <2120000.1110388509@[10.10.2.4]> (raw)
In-Reply-To: <20050309170915.GA1583@lnx-holt.americas.sgi.com>
> The "ideal" would be to have a node aware slab cache. Since that
> is probably a long time coming,
Manfred already did one. Perhaps we can get that going again? would
be useful for more than just this ...
M.
--
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>
next prev parent reply other threads:[~2005-03-09 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:09 Robin Holt
2005-03-09 17:15 ` Martin J. Bligh [this message]
2005-03-14 16:24 ` Robin Holt
2005-03-14 16:37 ` Martin J. Bligh
2005-03-09 19:32 ` Andrew Morton
2005-03-14 16:40 ` Robin Holt
2005-03-14 21:39 ` Andrew Morton
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='2120000.1110388509@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@intel.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