From: Andy Whitcroft <apw@shadowen.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc3-mm2 early_param mem= fix
Date: Mon, 07 Aug 2006 16:08:54 +0100 [thread overview]
Message-ID: <44D75786.8030603@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0608061829430.20012@blonde.wat.veritas.com>
Hugh Dickins wrote:
> On Sun, 6 Aug 2006, Hugh Dickins wrote:
>> I was impressed by how fast 2.6.18-rc3-mm2 is under memory pressure,
>> until I noticed that my "mem=512M" boot option was doing nothing. The
>> two fixes below got it working, but I wonder how many other early_param
>> "option=" args are wrong (e.g. "memmap=" in the same file): x86_64
>> shows many such, i386 shows only one, I've not followed it up further.
>
> Oh, and that's not enough for it to show up in x86_64's /proc/cmdline.
Thats one I've been chasing and is caused by this same patch. We've
lost the separation between command_line and saved_command_line and the
user visible line gets trunc'd. Andi has a later version which has this
part fixed as far as I can tell. I'm posting a dirty patch in response
to my report of this to at least get past this bit as our test system
relies on the commmand line being maintained to user space.
-apw
next prev parent reply other threads:[~2006-08-07 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 17:22 2.6.18-rc3-mm2 early_param mem= fix Hugh Dickins
2006-08-06 17:31 ` Hugh Dickins
2006-08-07 15:08 ` Andy Whitcroft [this message]
2006-08-07 21:09 ` Eric W. Biederman
2006-08-09 0:10 ` Keith Mannthey
2006-08-09 1:03 ` Andi Kleen
2006-08-09 1:27 ` Rusty Russell
2006-08-06 19:15 ` Andrew Morton
2006-08-07 2:06 ` Andi Kleen
2006-08-07 2:54 ` Rusty Russell
2006-08-07 2:55 ` Andi Kleen
2006-08-07 3:08 ` Rusty Russell
2006-08-07 3:13 ` Andi Kleen
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=44D75786.8030603@shadowen.org \
--to=apw@shadowen.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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