From: Linus Torvalds <torvalds@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-acpi@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org, petr@vandrovec.name,
akataria@vmware.com
Subject: Re: [Bug 25042] New: RAM buffer I/O resource badly interacts with memory hot-add
Date: Wed, 5 Jan 2011 18:20:15 -0800 [thread overview]
Message-ID: <AANLkTikF75EzTQAgCSVf-yGva2ioTHUVa2VTJ949EQ_q@mail.gmail.com> (raw)
In-Reply-To: <20110106111231.4fc98855.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, Jan 5, 2011 at 6:12 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> Hmm ? Why do you need to place "hot-added" memory's address range next to System
> RAM ? Sparsemem allows sparse memory layout.
Well, even without sparsemem, why couldn't the initial memory image
just be more nicely aligned to 256MB or something?
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-01-06 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25042-27@https.bugzilla.kernel.org/>
2011-01-04 21:51 ` [Bug 25042] New: RAM buffer I/O resource badly interacts with memory hot-add Andrew Morton
2011-01-04 22:32 ` Linus Torvalds
2011-01-04 23:55 ` Petr Vandrovec
2011-01-06 2:12 ` KAMEZAWA Hiroyuki
2011-01-06 2:20 ` Linus Torvalds [this message]
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=AANLkTikF75EzTQAgCSVf-yGva2ioTHUVa2VTJ949EQ_q@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=petr@vandrovec.name \
/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).