mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Willy Tarreau <willy@w.ods.org>
Cc: Josh Aas <josha@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.8.1 CPU Scheduler Documentation
Date: Mon, 14 Feb 2005 17:18:56 +1100	[thread overview]
Message-ID: <1108361936.5256.22.camel@npiggin-nld.site> (raw)
In-Reply-To: <20050214052812.GA31941@alpha.home.local>

On Mon, 2005-02-14 at 06:28 +0100, Willy Tarreau wrote:
> Hello Josh,
> 
> On Sun, Feb 13, 2005 at 06:23:15PM -0600, Josh Aas wrote:
> > Hello,
> > 
> > I have written an introduction to the Linux 2.6.8.1 CPU scheduler 
> > implementation. It should help people to understand what is going on in 
> > the scheduler code faster than they would be able to by just reading 
> > through the code. The paper can be downloaded in PDF or LyX form from 
> > here:
> > 
> > http://josh.trancesoftware.com/linux/
> 
> This is quite an interesting documentation.
> 

The multiprocessor scheduling documentation looks pretty
accurate, at a quick glance. A few small things though:

I don't think you place enough emphasis on the per-CPU-ness
of the 2.6 scheduler. For most workloads, this probably
yields by far the biggest improvement over the 2.4 scheduler
on even small SMP systems, due to much less lock and cacheline
contention.

Secondly, 7.1.2 can probably be removed completely. We can
actually handle this type of SMT balancing correctly without
shared runqueues (and in an arguably nicer way).

Nick



      reply	other threads:[~2005-02-14  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14  0:23 Josh Aas
2005-02-14  5:28 ` Willy Tarreau
2005-02-14  6:18   ` Nick Piggin [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=1108361936.5256.22.camel@npiggin-nld.site \
    --to=nickpiggin@yahoo.com.au \
    --cc=josha@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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®