public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marian Jancar <jancar@nmskb.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] O(1) scheduler, -G1, 2.5.2-pre10, 2.4.17 (fwd)
Date: Mon, 14 Jan 2002 09:40:23 +0100	[thread overview]
Message-ID: <3C429977.5000902@nmskb.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0201110142160.12174-100000@localhost.localdomain> <3C3F5C43.7060300@wanadoo.fr> <200201112150.g0BLoESr004177@svr3.applink.net>

Timothy Covell wrote:
...

>
>But, given the above case, what happens when you have Sendmail on
>the first CPU and Squid is sharing the second CPU?  This is not optimal
>either, or am I missing something?
>

It will not happen (unless you have ligth speed disks and nics) in this 
scenario, both squid and sendmail are io-hogs, not cpu.



  parent reply	other threads:[~2002-01-14  8:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 14:19 [patch] O(1) scheduler, -G1, 2.5.2-pre10, 2.4.17 (fwd) Ingo Molnar
2002-01-10 18:20 ` Linus Torvalds
2002-01-10 20:11   ` george anzinger
2002-01-10 23:54     ` Ingo Molnar
2002-01-10 23:22   ` Ingo Molnar
2002-01-11  0:01   ` Ingo Molnar
2002-01-10 20:01 ` Robert Love
2002-01-10 23:44   ` Ingo Molnar
2002-01-10 21:57 ` Mike Kravetz
2002-01-11  0:48   ` Ingo Molnar
2002-01-10 23:04     ` Davide Libenzi
2002-01-11 21:42     ` François Cami
2002-01-11 21:46       ` Timothy Covell
     [not found]         ` <1010814327.2018.5.camel@phantasy>
2002-01-12 11:48           ` François Cami
2002-01-12 16:26           ` Timothy Covell
2002-01-12 20:00             ` Robert Love
2002-01-12 20:44           ` Davide Libenzi
2002-01-12 20:44             ` Timothy Covell
2002-01-12 23:56             ` Robert Love
2002-01-13  6:59             ` Rusty Russell
2002-01-14  8:40         ` Marian Jancar [this message]
2002-01-11 21:53       ` Mark Hahn
  -- strict thread matches above, loose matches on Subject: below --
2002-01-13 20:30 Dieter Nützel

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=3C429977.5000902@nmskb.cz \
    --to=jancar@nmskb.cz \
    --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