mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Kravetz <kravetz@us.ibm.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC] Scheduler queue implementation ...
Date: Mon, 10 Dec 2001 15:03:42 -0800	[thread overview]
Message-ID: <20011210150342.C1124@w-mikek2.des.beaverton.ibm.com> (raw)
In-Reply-To: <E16DF5E-00009N-00@the-village.bc.nu> <Pine.LNX.4.40.0112091729180.996-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0112091729180.996-100000@blue1.dev.mcafeelabs.com>; from davidel@xmailserver.org on Sun, Dec 09, 2001 at 05:38:42PM -0800

On Sun, Dec 09, 2001 at 05:38:42PM -0800, Davide Libenzi wrote:
> Coming at the pipe example, let's take Larry's lat_ctx ( lmbench ).
> This is bouncing data through pipes using I/O bound tasks, and running
> vmstat together with a lat_ctx 32 32 ... ( long list ), you'll see the run
> queue length barley reach 3 ( with 32 bouncing tasks ).
> It barely reaches 5 with 64 bouncing tasks.

This may show my ignorance, but ... Why would one expect much
more than 2 runnable tasks as a result of a running lat_ctx?
This benchmark simply passes a token around a ring of tasks.  
One task awakens the next, then goes to sleep.  The only time
you have more than one runnable task is during the times when
the token is passed between tasks.  In these transition times
I would rarely expect more than 2 tasks on the runqueue no
matter how many bouncing tasks you have. 

We created a benchmark similar to lat_ctx that would allow you
to control how many runnable tasks there are in the system.
Look for 'Reflex' benchmark at:
http://lse.sourceforge.net/scheduling/
You can think of this as a controlled way of running multiple
copies of lat_ctx in parallel.

-- 
Mike

  parent reply	other threads:[~2001-12-10 23:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10  0:33 Davide Libenzi
2001-12-10  0:49 ` Alan Cox
2001-12-10  0:57   ` Davide Libenzi
2001-12-10  1:16     ` Alan Cox
2001-12-10  2:36       ` Davide Libenzi
2001-12-20 19:36       ` Pavel Machek
2001-12-20 21:42         ` Rik van Riel
2001-12-21 17:01         ` Alan Cox
2001-12-21 19:21           ` Pavel Machek
2001-12-22 14:23             ` Alan Cox
2001-12-10  0:52 ` Alan Cox
2001-12-10  1:06   ` Davide Libenzi
2001-12-10  1:18     ` Alan Cox
2001-12-10  1:38       ` Davide Libenzi
2001-12-10  1:52         ` Alan Cox
2001-12-10  3:06           ` Davide Libenzi
2001-12-10 23:03         ` Mike Kravetz [this message]
2001-12-10 23:30           ` Davide Libenzi

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=20011210150342.C1124@w-mikek2.des.beaverton.ibm.com \
    --to=kravetz@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®