From: Christoph Lameter <clameter@engr.sgi.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, alokk@calsoftinc.com
Subject: Re: [RFC, PATCH] Slab counter troubles with swap prefetch?
Date: Fri, 11 Nov 2005 09:43:22 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511110941050.20360@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200511111450.07396.kernel@kolivas.org>
On Fri, 11 Nov 2005, Con Kolivas wrote:
> One last thing. Swap prefetch works off the accounting of total memory and is
> only a single kernel thread rather than a thread per cpu or per pgdat unlike
> kswapd. Currently it just cares about total slab data and total ram.
> Depending on where this thread is scheduled (which node) your accounting
> change will alter the behaviour of it. Does this affect the relevance of this
> patch to you?
Yes, if its a truly global value then we would not need the patch.
But then the prefetch code would have to add up all the nr_slab field for
all processors and use that result for comparison. If you do this in a
node specific fashion then the problem comes up again.
--
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>
prev parent reply other threads:[~2005-11-11 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 21:55 Christoph Lameter
2005-11-10 23:07 ` Con Kolivas
2005-11-10 23:13 ` Christoph Lameter
2005-11-10 23:17 ` Con Kolivas
2005-11-11 3:50 ` Con Kolivas
2005-11-11 17:43 ` Christoph Lameter [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=Pine.LNX.4.62.0511110941050.20360@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=alokk@calsoftinc.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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