From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: "Serge E. Hallyn" <serge@hallyn.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Paul Jackson <pj@sgi.com>,
clameter@sgi.com, dhaval@linux.vnet.ibm.com, bob.picco@hp.com,
nacc@us.ibm.com, kamezawa.hiroyu@jp.fujitsu.com, mel@skynet.ie,
balbir@in.ibm.com, vatsa@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net
Subject: Re: Regression in 2.6.23-rc2-mm2, mounting cpusets causes a hang
Date: Wed, 15 Aug 2007 14:00:29 -0400 [thread overview]
Message-ID: <1187200830.5422.39.camel@localhost> (raw)
In-Reply-To: <20070815171210.GB13286@vino.hallyn.com>
On Wed, 2007-08-15 at 12:12 -0500, Serge E. Hallyn wrote:
> Quoting Paul Jackson (pj@sgi.com):
> > Lee wrote:
> > > [altho' methinks CPUSET should select CONTAINERS rather than
> > > depend on it...]
> >
> > Good point -- what do you think, Paul Menage?
>
> Paul mentioned (http://www.spinics.net/lists/linux-containers/msg03775.html)
> that he was asked not to use select in Kconfigs any more.
That is unfortunate. I view CPUSET is a "first class" option that
happens to be built on CONTAINERS. IMO, I shouldn't have to know this
implementation detail in order to select CPUSET--indeed, even to be
offered the optio--in 'make *config'. However, it will be hidden if I
haven't already selected containers. Or do I misunderstand the
implications of "depends on"?
Andrew: is the problem with select something fatal or just too
difficult to fix?
Lee
next prev parent reply other threads:[~2007-08-15 18:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 15:21 Regression in 2.6.23-rc2-mm2, mounting cpusets causes a hang Dhaval Giani
2007-08-13 20:12 ` Serge E. Hallyn
2007-08-14 15:03 ` Lee Schermerhorn
2007-08-14 18:03 ` Serge E. Hallyn
2007-08-14 18:13 ` Lee Schermerhorn
2007-08-14 19:23 ` Serge E. Hallyn
2007-08-14 20:49 ` Serge E. Hallyn
2007-08-14 21:07 ` Lee Schermerhorn
2007-08-14 21:28 ` Christoph Lameter
2007-08-14 21:41 ` Lee Schermerhorn
2007-08-14 21:56 ` Christoph Lameter
2007-08-15 13:43 ` Lee Schermerhorn
2007-08-15 14:31 ` Serge E. Hallyn
2007-08-15 16:23 ` Lee Schermerhorn
2007-08-15 16:31 ` Serge E. Hallyn
2007-08-15 16:52 ` Dhaval Giani
2007-08-15 17:08 ` Serge E. Hallyn
2007-08-15 18:07 ` Lee Schermerhorn
2007-08-15 20:39 ` Christoph Lameter
2007-08-16 13:26 ` Lee Schermerhorn
2007-08-16 19:14 ` Christoph Lameter
2007-08-15 20:38 ` Christoph Lameter
2007-08-15 16:31 ` Paul Jackson
2007-08-15 16:29 ` Paul Jackson
2007-08-15 17:12 ` Serge E. Hallyn
2007-08-15 18:00 ` Lee Schermerhorn [this message]
2007-08-15 18:33 ` Andrew Morton
2007-08-31 16:54 ` [ckrm-tech] " Paul Menage
2007-08-16 4:46 ` Paul Menage
2007-08-15 20:36 ` Christoph Lameter
2007-08-15 20:48 ` Lee Schermerhorn
2007-08-16 2:36 ` [ckrm-tech] " Paul Jackson
2007-08-14 21:37 ` Lee Schermerhorn
2007-08-14 21:39 ` Christoph Lameter
2007-08-14 21:01 ` Lee Schermerhorn
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=1187200830.5422.39.camel@localhost \
--to=lee.schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=bob.picco@hp.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=clameter@sgi.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@skynet.ie \
--cc=nacc@us.ibm.com \
--cc=pj@sgi.com \
--cc=serge@hallyn.com \
--cc=vatsa@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.