From: Andi Kleen <ak@muc.de>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Option to run cache reap in thread mode
Date: Wed, 16 Jun 2004 18:22:28 +0200 [thread overview]
Message-ID: <m3r7sfmq0r.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <27JKg-4ht-11@gated-at.bofh.it> (Dimitri Sivanich's message of "Wed, 16 Jun 2004 16:40:16 +0200")
Dimitri Sivanich <sivanich@sgi.com> writes:
> I would like to know what others think about running cache_reap() as a low
> priority realtime kthread, at least on certain cpus that would be configured
> that way (probably configured at boottime initially). I've been doing some
> testing running it this way on CPU's whose activity is mostly restricted to
> realtime work (requiring rapid response times).
>
> Here's my first cut at an initial patch for this (there will be other changes
> later to set the configuration and to optimize locking in cache_reap()).
I would run it in the standard work queue threads. We already have
too many kernel threads, no need to add more.
Also is there really a need for it to be real time?
Note that we don't make any attempt at all in the linux kernel to handle
lock priority inversion, so this isn't an argument.
-Andi
next parent reply other threads:[~2004-06-16 16:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27JKg-4ht-11@gated-at.bofh.it>
2004-06-16 16:22 ` Andi Kleen [this message]
2004-06-16 18:16 ` [PATCH]: Option to run cache reap in thread mode Dimitri Sivanich
2004-06-16 17:23 Manfred Spraul
2004-06-16 18:02 ` Dimitri Sivanich
2004-06-16 18:58 ` Manfred Spraul
2004-06-17 13:10 ` Dimitri Sivanich
2004-06-18 4:40 ` Andrew Morton
2004-06-18 14:33 ` Dimitri Sivanich
2004-06-18 20:40 ` Andrew Morton
2004-06-18 21:04 ` Manfred Spraul
2004-06-18 21:44 ` Dimitri Sivanich
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 14:24 Dimitri Sivanich
2004-06-16 15:29 ` Christoph Hellwig
2004-06-16 16:03 ` Dimitri Sivanich
2004-06-16 16:07 ` Christoph Hellwig
2004-06-16 16:25 ` Jesse Barnes
2004-06-16 16:51 ` Dimitri Sivanich
2004-06-16 16:46 ` Lori Gilbertson
2004-06-16 16:53 ` Christoph Hellwig
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=m3r7sfmq0r.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox