From: "Chris Friesen" <cfriesen@nortel.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Andrew Morton <akpm@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
sam@vilain.net, vatsa@in.ibm.com, dev@openvz.org, mingo@elte.hu,
pwil3058@bigpond.net.au, sekharan@us.ibm.com, balbir@in.ibm.com,
linux-kernel@vger.kernel.org, maeda.naoaki@jp.fujitsu.com,
kurosawa@valinux.co.jp
Subject: Re: [RFC] CPU controllers?
Date: Mon, 19 Jun 2006 12:21:34 -0600 [thread overview]
Message-ID: <4496EB2E.2000106@nortel.com> (raw)
In-Reply-To: <1150616176.7985.50.camel@Homer.TheSimpsons.net>
Mike Galbraith wrote:
> Scheduling contexts do sound useful. They're easily defeated though, as
> evolution mail demonstrates to me every time it's GUI hangs and I see
> that a nice 19 find is running, eating very little CPU, but effectively
> DoSing evolution nonetheless (journal). I wonder how often people who
> tried to distribute CPU would likewise be stymied by other resources.
We do a lot with diskless blades. Basically cpu(s), memory, and network
ports.
For this case, cpu, memory, and network controllers are sufficient.
Even just cpu gets you a long way, since mostly we're not IO-intensive
and we generally have a pretty good idea of memory consumption.
Chris
next prev parent reply other threads:[~2006-06-19 18:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 13:46 [RFC] CPU controllers? Srivatsa Vaddagiri
2006-06-15 21:52 ` Sam Vilain
2006-06-15 23:30 ` Peter Williams
2006-06-16 0:42 ` Matt Helsley
2006-06-17 8:48 ` Nick Piggin
2006-06-17 15:55 ` Balbir Singh
2006-06-17 16:48 ` Srivatsa Vaddagiri
2006-06-18 5:06 ` Nick Piggin
2006-06-18 5:53 ` Sam Vilain
2006-06-18 6:11 ` Nick Piggin
2006-06-18 6:40 ` Sam Vilain
2006-06-18 7:17 ` Nick Piggin
2006-06-18 6:42 ` Andrew Morton
2006-06-18 7:28 ` Nick Piggin
2006-06-19 19:03 ` Resource Management Requirements (was "[RFC] CPU controllers?") Chandra Seetharaman
2006-06-20 5:40 ` Srivatsa Vaddagiri
2006-06-18 7:36 ` [RFC] CPU controllers? Mike Galbraith
2006-06-18 7:49 ` Nick Piggin
2006-06-18 7:49 ` Nick Piggin
2006-06-18 9:09 ` Andrew Morton
2006-06-18 9:49 ` Mike Galbraith
2006-06-19 6:28 ` Mike Galbraith
2006-06-19 6:35 ` Andrew Morton
2006-06-19 6:46 ` Mike Galbraith
2006-06-19 18:21 ` Chris Friesen [this message]
2006-06-20 6:20 ` Mike Galbraith
2006-06-18 7:18 ` Srivatsa Vaddagiri
2006-06-19 2:07 ` Sam Vilain
2006-06-19 7:04 ` MAEDA Naoaki
2006-06-19 8:19 ` Sam Vilain
2006-06-19 8:41 ` MAEDA Naoaki
2006-06-19 8:53 ` Sam Vilain
2006-06-19 21:44 ` MAEDA Naoaki
2006-06-19 18:14 ` Chris Friesen
2006-06-19 19:11 ` Chandra Seetharaman
2006-06-19 20:28 ` Chris Friesen
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=4496EB2E.2000106@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=dev@openvz.org \
--cc=efault@gmx.de \
--cc=kurosawa@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=maeda.naoaki@jp.fujitsu.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
--cc=sam@vilain.net \
--cc=sekharan@us.ibm.com \
--cc=vatsa@in.ibm.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