From: Manfred Spraul <manfred@colorfullife.com>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org, lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: [PATCH]: Option to run cache reap in thread mode
Date: Wed, 16 Jun 2004 19:23:49 +0200 [thread overview]
Message-ID: <40D08225.6060900@colorfullife.com> (raw)
Dimitri wrote:
>In the process of testing per/cpu interrupt response times and CPU availability,
>I've found that running cache_reap() as a timer as is done currently results
>in some fairly long CPU holdoffs.
>
What is fairly long?
If cache_reap() is slow than the caches are too large.
Could you limit cachep->free_limit and check if that helps? It's right
now scaled by num_online_cpus() - that's probably too much. It's
unlikely that all 500 cpus will try to refill their cpu arrays at the
same time. Something like a logarithmic increase should be sufficient.
Do you use the default batchcount values or have you increased the values?
I think the sgi ia64 system do not work with slab debugging, but please
check that debugging is off. Debug enabled is slow.
--
Manfred
next reply other threads:[~2004-06-16 17:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 17:23 Manfred Spraul [this message]
2004-06-16 18:02 ` [PATCH]: Option to run cache reap in thread mode Dimitri Sivanich
2004-06-16 18:02 ` Dimitri Sivanich
2004-06-16 18:58 ` Manfred Spraul
2004-06-16 18:58 ` Manfred Spraul
2004-06-17 13:10 ` Dimitri Sivanich
2004-06-17 13:10 ` Dimitri Sivanich
2004-06-18 4:40 ` Andrew Morton
2004-06-18 4:40 ` Andrew Morton
2004-06-18 14:33 ` Dimitri Sivanich
2004-06-18 14:33 ` Dimitri Sivanich
2004-06-18 20:40 ` Andrew Morton
2004-06-18 20:40 ` Andrew Morton
2004-06-18 21:04 ` Manfred Spraul
2004-06-18 21:04 ` Manfred Spraul
2004-06-18 21:44 ` Dimitri Sivanich
2004-06-18 21:44 ` Dimitri Sivanich
2004-06-18 22:03 ` Andrew Morton
2004-06-18 22:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 16:43 Mark_H_Johnson
2004-06-16 16:43 ` Mark_H_Johnson
[not found] <27JKg-4ht-11@gated-at.bofh.it>
2004-06-16 16:22 ` Andi Kleen
2004-06-16 18:16 ` Dimitri Sivanich
2004-06-16 18:16 ` Dimitri Sivanich
2004-06-16 14:24 Dimitri Sivanich
2004-06-16 14:24 ` Dimitri Sivanich
2004-06-16 15:29 ` Christoph Hellwig
2004-06-16 15:29 ` Christoph Hellwig
2004-06-16 16:03 ` Dimitri Sivanich
2004-06-16 16:03 ` Dimitri Sivanich
2004-06-16 16:07 ` Christoph Hellwig
2004-06-16 16:07 ` Christoph Hellwig
2004-06-16 16:25 ` Jesse Barnes
2004-06-16 16:25 ` Jesse Barnes
2004-06-16 16:51 ` Dimitri Sivanich
2004-06-16 16:51 ` Dimitri Sivanich
2004-06-16 16:46 ` Lori Gilbertson
2004-06-16 16:46 ` Lori Gilbertson
2004-06-16 16:53 ` Christoph Hellwig
2004-06-16 16:53 ` Christoph Hellwig
2004-06-16 21:30 ` Andrew Morton
2004-06-16 21:30 ` 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=40D08225.6060900@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=sivanich@sgi.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.