From: Peter Zijlstra <peterz@infradead.org>
To: Lennart Poettering <mzxreary@0pointer.de>
Cc: Dhaval Giani <dhaval.giani@gmail.com>,
James Kosin <jkosin@intcomgrp.com>,
linux-kernel@vger.kernel.org, menage@google.com,
balbir@linux.vnet.ibm.com, jsafrane@redhat.com,
tglx@linutronix.de
Subject: Re: [PATCH/RFC] Have sane default values for cpusets
Date: Fri, 14 May 2010 09:23:41 +0200 [thread overview]
Message-ID: <1273821821.5605.3572.camel@twins> (raw)
In-Reply-To: <1273819904.5605.3562.camel@twins>
On Fri, 2010-05-14 at 08:51 +0200, Peter Zijlstra wrote:
> Init using the bare minimum possible only seems like a sensible thing.
> Once the basic stuff is running you can detect whats available and use
> it if needed/wanted.
I really think init should be able to run regardless of any CONFIG_*
option. The only thing that should avoid init from running is not being
able to mount the filesystem with init on it.
next prev parent reply other threads:[~2010-05-14 7:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eJjRf-6YM-1@gated-at.bofh.it>
[not found] ` <eJktY-7JG-7@gated-at.bofh.it>
[not found] ` <eJktY-7JG-5@gated-at.bofh.it>
2010-05-12 14:11 ` [PATCH/RFC] Have sane default values for cpusets James Kosin
2010-05-12 14:13 ` Dhaval Giani
2010-05-12 14:20 ` Peter Zijlstra
2010-05-12 14:22 ` Dhaval Giani
2010-05-12 14:40 ` Jan Safranek
[not found] ` <4BEAE7A1.2010001@intcomgrp.com>
2010-05-12 17:42 ` Dhaval Giani
2010-05-12 17:58 ` James Kosin
2010-05-12 18:04 ` Chris Friesen
2010-05-12 18:27 ` Balbir Singh
2010-05-12 19:07 ` Lennart Poettering
2010-05-13 13:01 ` Peter Zijlstra
2010-05-13 14:03 ` Lennart Poettering
2010-05-13 20:06 ` Paul Menage
2010-05-13 20:36 ` Lennart Poettering
2010-05-13 20:41 ` Lennart Poettering
2010-05-13 21:07 ` Balbir Singh
2010-05-13 23:55 ` Lennart Poettering
2010-05-14 5:44 ` Balbir Singh
2010-05-14 6:34 ` Dhaval Giani
2010-05-13 21:29 ` Paul Menage
2010-05-13 21:19 ` Peter Zijlstra
2010-05-14 0:02 ` Lennart Poettering
2010-05-14 5:43 ` Balbir Singh
2010-05-14 6:53 ` Peter Zijlstra
2010-05-14 8:12 ` Balbir Singh
2010-05-14 10:38 ` Peter Zijlstra
2010-05-14 11:57 ` Dhaval Giani
2010-05-14 16:07 ` Lennart Poettering
2010-05-14 6:51 ` Peter Zijlstra
2010-05-14 7:23 ` Peter Zijlstra [this message]
2010-05-14 8:11 ` Balbir Singh
2010-05-12 13:05 Dhaval Giani
2010-05-12 13:40 ` Peter Zijlstra
2010-05-12 13:46 ` Dhaval Giani
2010-05-12 19:01 ` Paul Menage
2010-05-12 19:10 ` Dhaval Giani
2010-05-12 19:20 ` Paul Menage
2010-05-12 19:29 ` Dhaval Giani
2010-05-12 19:36 ` Paul Menage
2010-05-12 19:39 ` Balbir Singh
2010-05-12 19:59 ` Dhaval Giani
2010-05-13 10:26 ` Dhaval Giani
2010-05-13 10:52 ` Balbir Singh
2010-05-13 20:12 ` Paul Menage
2010-05-13 20:16 ` Dhaval Giani
2010-05-13 20:19 ` Dhaval Giani
2010-05-12 19:30 ` Balbir Singh
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=1273821821.5605.3572.camel@twins \
--to=peterz@infradead.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=dhaval.giani@gmail.com \
--cc=jkosin@intcomgrp.com \
--cc=jsafrane@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mzxreary@0pointer.de \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).