[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1187200830.5422.39.camel@localhost>
Date: Wed, 15 Aug 2007 14:00:29 -0400
From: Lee Schermerhorn <Lee.Schermerhorn@...com>
To: "Serge E. Hallyn" <serge@...lyn.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Paul Jackson <pj@....com>, clameter@....com,
dhaval@...ux.vnet.ibm.com, bob.picco@...com, nacc@...ibm.com,
kamezawa.hiroyu@...fujitsu.com, mel@...net.ie, balbir@...ibm.com,
vatsa@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
ckrm-tech@...ts.sourceforge.net
Subject: Re: Regression in 2.6.23-rc2-mm2, mounting cpusets causes a hang
On Wed, 2007-08-15 at 12:12 -0500, Serge E. Hallyn wrote:
> Quoting Paul Jackson (pj@....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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists