From: Werner Almesberger <wa@almesberger.net>
To: Andi Kleen <ak@suse.de>
Cc: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>,
Adrian Bunk <bunk@stusta.de>,
Janos Farkas <jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org>,
linux-kernel@vger.kernel.org, Chris Bruner <cryst@golden.net>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Matt Domsch <Matt_Domsch@dell.com>
Subject: Re: COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6
Date: Mon, 7 Feb 2005 03:57:07 -0300 [thread overview]
Message-ID: <20050207035707.C25338@almesberger.net> (raw)
In-Reply-To: <20050121071144.GB657@wotan.suse.de>; from ak@suse.de on Fri, Jan 21, 2005 at 08:11:44AM +0100
Andi Kleen wrote:
> It's dependent on the architecture already. I would like to enable
> it on i386/x86-64 because the kernel command line is often used
> to pass parameters to installers, and having a small limit there
> can be awkward.
Something to keep in mind when extending the command line is that
we'll probably need a mechanism for passing additional (and
possibly large) data blocks from the boot loader soon.
The reason for this is that, if booting through kexec, it would be
attractive to pass device scan results, so that the second kernel
doesn't have to repeat the work. As an obvious extension, anyone
who wants to boot *quickly* could also pass such data from
persistent storage without actually performing the device scan at
all when the machine is booted.
The command line may be suitable for this, but to allow for passing
a lot of data, its place in memory should perhaps just be reserved,
at least until the system has passed initialization, without trying
to copy it to a "safe" place early in kernel startup.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2005-02-07 6:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 23:13 Janos Farkas
2005-01-20 4:21 ` Chris Bruner
2005-01-20 16:28 ` Adrian Bunk
2005-01-20 16:40 ` Linus Torvalds
2005-01-20 16:48 ` Andi Kleen
2005-01-20 20:53 ` Something very strange on x86_64 2.6.X kernels Eric Dumazet
2005-01-20 21:08 ` Andrew Morton
2005-01-20 21:19 ` Eric Dumazet
2005-01-21 16:26 ` Petr Vandrovec
2005-01-21 16:49 ` Eric Dumazet
2005-01-21 18:30 ` Petr Vandrovec
2005-01-22 1:54 ` Andi Kleen
2005-01-22 2:14 ` Linus Torvalds
2005-01-21 6:58 ` COMMAND_LINE_SIZE increasing in 2.6.11-rc1-bk6 Catalin(ux aka Dino) BOIE
2005-01-21 7:11 ` Andi Kleen
2005-01-21 17:46 ` Matt Domsch
2005-01-21 19:05 ` H. Peter Anvin
2005-02-07 6:57 ` Werner Almesberger [this message]
2005-02-12 13:54 ` Eric W. Biederman
2005-02-12 14:51 ` Werner Almesberger
2005-02-12 15:17 ` Eric W. Biederman
2005-02-14 5:49 ` Werner Almesberger
2005-02-14 7:36 ` Eric W. Biederman
2005-02-14 6:15 ` Adam Sulmicki
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=20050207035707.C25338@almesberger.net \
--to=wa@almesberger.net \
--cc=Matt_Domsch@dell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=cryst@golden.net \
--cc=jf-ml-k1-1087813225@lk8rp.mail.xeon.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=util@deuroconsult.ro \
/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
Powered by JetHome