From: Paul Jackson <pj@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: felix@obenhuber.de, linux-kernel@vger.kernel.org,
dynsched-devel@lists.sourceforge.net, menage@google.com
Subject: Re: [RFC] dynsched - different cpu schedulers per cpuset
Date: Wed, 29 Nov 2006 20:48:51 -0800 [thread overview]
Message-ID: <20061129204851.ecc7dbb0.pj@sgi.com> (raw)
In-Reply-To: <20061129201310.54da1618.pj@sgi.com>
pj wrote:
> See Paul Menage's most recent patch proposal at:
> http://lkml.org/lkml/2006/11/17/217
> Subject: [PATCH 0/6] Multi-hierarchy Process Containers
> Date: Fri, 17 Nov 2006 11:11:59 -0800
I'm behind the times. Paul Menage's most recent proposal is at:
http://lkml.org/lkml/2006/11/23/95
Subject: [PATCH 0/7] Generic Process Containers (+ ResGroups/BeanCounters)
Date: Thu, 23 Nov 2006 04:08:48 -0800
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-11-30 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 16:06 [RFC] dynsched - different cpu schedulers per cpuset Felix Obenhuber
2006-11-30 4:13 ` Paul Jackson
2006-11-30 4:48 ` Paul Jackson [this message]
2006-11-30 8:08 ` Paul Menage
2006-11-30 19:40 ` Felix Obenhuber
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=20061129204851.ecc7dbb0.pj@sgi.com \
--to=pj@sgi.com \
--cc=dynsched-devel@lists.sourceforge.net \
--cc=felix@obenhuber.de \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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