From: Mike Fedyk <mfedyk@matchmail.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH]O20int
Date: Wed, 3 Sep 2003 17:12:14 -0700 [thread overview]
Message-ID: <20030904001214.GH16361@matchmail.com> (raw)
In-Reply-To: <200309040855.46034.kernel@kolivas.org>
On Thu, Sep 04, 2003 at 08:55:45AM +1000, Con Kolivas wrote:
> On Thu, 4 Sep 2003 05:19, Mike Fedyk wrote:
> > On Thu, Sep 04, 2003 at 12:53:10AM +1000, Con Kolivas wrote:
> > > Smaller timeslice granularity for most interactive tasks and larger for
> > > less interactive. Smaller for each extra cpu.
> > >
> > > +#ifdef CONFIG_SMP
> > > +#define TIMESLICE_GRANULARITY(p) \
> > > + (MIN_TIMESLICE * (1 << (MAX_BONUS - CURRENT_BONUS(p))) * \
> > > + num_online_cpus())
> > > +#else
> > > +#define TIMESLICE_GRANULARITY(p) \
> > > + (MIN_TIMESLICE * (1 << (MAX_BONUS - CURRENT_BONUS(p))))
> > > +#endif
> > > +
> >
> > Don't you want to put a max(10,TIMESLICE_GRANULARITY) in there so that the
> > time slice won't go below 1ms for large proc servers? I'm not sure if it
> > was you, or someone else but they did some testing to see how the
> > timeslice length affected the cache warmth, and the major improvements
> > stopped after 7ms, so 10 might be a good default mimimum.
>
> That works out to 10ms minimum.
With how many processors? 64? 128?
next prev parent reply other threads:[~2003-09-04 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 14:53 [PATCH]O20int Con Kolivas
2003-09-03 19:19 ` [PATCH]O20int Mike Fedyk
2003-09-03 22:55 ` [PATCH]O20int Con Kolivas
2003-09-04 0:12 ` Mike Fedyk [this message]
2003-09-04 0:27 ` [PATCH]O20int Con Kolivas
2003-09-04 1:52 ` [PATCH]O20int Mike Fedyk
2003-09-07 5:41 ` [PATCH]O20int Matt Heler
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=20030904001214.GH16361@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--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