From: Pavel Machek <pavel@ucw.cz>
To: Dave Jones <davej@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
alon.barlev@gmail.com, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64, i386: Add command line length to boot protocol
Date: Tue, 13 Mar 2007 00:12:20 +0100 [thread overview]
Message-ID: <20070312231220.GC9749@elf.ucw.cz> (raw)
In-Reply-To: <20070312205513.GC21835@redhat.com>
Hi!
> > > > +cmdline_size: .long COMMAND_LINE_SIZE-1 #length of the command line,
> > >
> > > Why a long? It's unlikely that someone is going to have a command line
> > > bigger than 0xffff.
> >
> > Well, I could imagine overflowing that. Describing your numa setup,
> > excluding few bad bits of ram using memmap=exact, set up your boot
> > over iscsi on cmdline.... these are likely to eat insane ammount of
> > cmdline space.
>
> 65535 characters? Are you for real?
> Stop and think about just how big that is. If you have to create
> a boot command line that long, you have serious, serious issues.
Well, it is about the same size as my .config...
I agree we are unlikely to hit it any time soon... I could imagine
some (ab)uses, like fixed_acpi_bios=<lots of hex digits>, but those
are ugly. I could also imagine some uses where entire embedded machine
is described at kernel commandline.
Yes, all those are ugly/unlikely. OTOH saving 2 bytes does not seem
like that great goal.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-03-12 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 18:14 [PATCH] x86_64, i386: Add command line length to boot protocol Bernhard Walle
2007-03-06 18:21 ` Dave Jones
2007-03-12 10:43 ` Pavel Machek
2007-03-12 20:55 ` Dave Jones
2007-03-12 23:12 ` Pavel Machek [this message]
2007-03-12 23:39 ` Dave Jones
2007-03-06 21:46 ` Alon Bar-Lev
2007-03-07 10:05 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2007-02-13 16:49 Bernhard Walle
2007-02-04 18:05 Bernhard Walle
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=20070312231220.GC9749@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alon.barlev@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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