mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davidel@xmailserver.org (Davide Libenzi)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	linux-kernel@vger.kernel.org (lkml),
	torvalds@transmeta.com (Linus Torvalds)
Subject: Re: [RFC] Scheduler queue implementation ...
Date: Mon, 10 Dec 2001 01:18:16 +0000 (GMT)	[thread overview]
Message-ID: <E16DF5E-00009N-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.40.0112091701000.996-100000@blue1.dev.mcafeelabs.com> from "Davide Libenzi" at Dec 09, 2001 05:06:04 PM

> > of non cpu hog processes running. A lot of messaging systems have high task
> > switch rates but very few cpu hogs. So you still need to handle the non hogs
> > carefully to avoid degenerating back into Linus scheduler.
> 
> In my experience, if you've I/O bound tasks that lead to a long run queue,
> that means that you're suffering major kernel latency problems ( other than the
> scheduler ).

I don't see any evidence of it in the profiles. Its just that a lot of stuff
gets passed around between multiple daemons. You can see similar things
in something as mundane as a 4 task long pipe, a user mode file system or
some X11 clients.

  reply	other threads:[~2001-12-10  1:11 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 [this message]
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
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=E16DF5E-00009N-00@the-village.bc.nu \
    --to=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®