public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: Rob Landley <rob@landley.net>
Cc: tglx@linutronix.de, Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86: add max_addr boot option
Date: Wed, 23 May 2012 09:23:19 +0800	[thread overview]
Message-ID: <4FBC3C07.5010201@cn.fujitsu.com> (raw)
In-Reply-To: <4FBBEE49.2020806@landley.net>

At 05/23/2012 03:51 AM, Rob Landley Wrote:
> On 05/22/2012 02:02 AM, Wen Congyang wrote:
>> If we only want to use node0, we can specify the max_addr. The boot
>> option "mem=" can do the same thing now. But the boot option "mem="
>> means the total memory used by the system. If we tell the user
>> that the boot option "mem=" can do this, it will confuse the user.
>> So we need an new boot option "max_addr" on x86 platform.
> 
> I didn't follow that reasoning at all.  Care to try again?
> 
> (mem= can do this, but telling users that would confuse them?  What?)

mem= means the total memory, but we implement it as max address.
I donot know why we implement it as max address. The users donot
know how we implement, and they only know that they can use
mem= to set the total memory. If you tell the users that mem=
can set max address, it will confuse them.

Thanks
Wen Congyang

> 
> Rob


  reply	other threads:[~2012-05-23  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  7:02 [PATCH 1/2] x86: add max_addr boot option Wen Congyang
2012-05-22  7:05 ` [PATCH 2/2] x86: reimplement mem " Wen Congyang
2012-05-22 19:51 ` [PATCH 1/2] x86: add max_addr " Rob Landley
2012-05-23  1:23   ` Wen Congyang [this message]
2012-05-23  4:06   ` KAMEZAWA Hiroyuki
2012-05-23 14:25 ` Bjorn Helgaas
2012-05-24  5:19   ` Wen Congyang

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=4FBC3C07.5010201@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rob@landley.net \
    --cc=tglx@linutronix.de \
    --cc=x86@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