From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: David Mosberger <davidm@napali.hpl.hp.com>, linux-kernel@vger.kernel.org
Subject: Re: add /proc/sys/kernel/cache_decay_ticks
Date: Wed, 18 Jun 2003 15:12:42 -0700 [thread overview]
Message-ID: <16112.58330.522570.329438@napali.hpl.hp.com> (raw)
In-Reply-To: <p73znkf2g9t.fsf@oldwotan.suse.de>
>>>>> On 19 Jun 2003 00:05:18 +0200, Andi Kleen <ak@suse.de> said:
Andi> David Mosberger <davidm@napali.hpl.hp.com> writes:
>> /proc/sys/kernel/cache_decay_ticks allows runtime tuning of the
>> scheduler. The earlier patch collided with the C99-ification of
>> the file, so here is a retransmit.
Andi> Funny, I did a similar patch for 2.4 a short time ago. But I
Andi> would suggest one change before you merge that to
Andi> mainline. The variable is currently used like this:
Andi> #define CAN_MIGRATE_TASK(p,rq,this_cpu) \ ((jiffies -
Andi> (p)->last_run > cache_decay_ticks) && \o
Andi> Which means 0 means 1 jiffie. For a tunable it would be useful
Andi> to be able to turn it off completely, which means the > needs
Andi> to be replaced with a >=. Unfortunately this requires changes
Andi> in the architectures too to subtract one. But it would make it
Andi> more useful. I would do the change before exposing it.
I don't see why the two have to be tied together. I agree it would be
_nice_, but having /proc/sys/kernel/cache_decay_ticks in it's current
form is much better than nothing at all.
--david
next prev parent reply other threads:[~2003-06-18 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200306182151.h5ILpMcx022062@napali.hpl.hp.com.suse.lists.linux.kernel>
2003-06-18 22:05 ` Andi Kleen
2003-06-18 22:12 ` David Mosberger [this message]
2003-06-18 22:18 ` Andi Kleen
2003-06-18 21:51 David Mosberger
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=16112.58330.522570.329438@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=ak@suse.de \
--cc=davidm@hpl.hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®