From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Matthew E Tolentino <matthew.e.tolentino@intel.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lhms <lhms-devel@lists.sourceforge.net>,
Andrew Morton <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
"Luck, Tony" <tony.luck@intel.com>,
Hirokazu Takahashi <taka@valinux.co.jp>,
Dave McCracken <dmccr@us.ibm.com>
Subject: Re: [PATCH] no buddy bitmap patch : intro and includes [0/2]
Date: Fri, 08 Oct 2004 09:51:40 +0900 [thread overview]
Message-ID: <4165E49C.6080604@jp.fujitsu.com> (raw)
In-Reply-To: <1260090000.1097164623@[10.10.2.4]>
Martin J. Bligh wrote:
>>>>What was the purpose behind this, again? Sorry, has been too long since
>>>>I last looked.
>>On Thu, 2004-10-07 at 08:03, Tolentino, Matthew E wrote:
>>
>>For one, it avoids the otherwise requisite resizing of the bitmaps=20
>>during memory hotplug operations...
>>
>> Dave McCracken wrote:
>> The memory allocator bitmaps are the main remaining reason we need the
>> concept of linear memory. If we can get rid of them, it's one step closer
>> to managing memory as a set of sections.
>>--Dave Hansen <haveblue@us.ibm.com> wrote (on Thursday, October 07, 2004 08:39:38 -0700)
>>It also simplifies the nonlinear implementation. The whole reason we
>>had the lpfn (Linear) stuff was so that the bitmaps could represent a
>>sparse physical address space in a much more linear fashion. With no
>>bitmaps, this isn't an issue, and gets rid of a lot of code, and a
>>*huge* source of bugs where lpfns and pfns are confused for each other.
>
>
> Makese sense on both counts. Would be nice to add the justification to
> the changelog ;-)
>
It seems all I should answer is already answered.
Thank you all.
I'll add the purpose to the changelog.
Kame <kamezawa.hiroyu@jp.fujitsu.com>
> M.
>
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-08 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 15:03 [Lhms-devel] " Tolentino, Matthew E
2004-10-07 15:39 ` Dave Hansen
2004-10-07 15:57 ` Martin J. Bligh
2004-10-07 16:10 ` Dave Hansen
2004-10-07 16:17 ` Martin J. Bligh
2004-10-07 17:56 ` Martin J. Bligh
2004-10-08 0:51 ` Hiroyuki KAMEZAWA [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 12:22 Hiroyuki KAMEZAWA
2004-10-07 14:45 ` Martin J. Bligh
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=4165E49C.6080604@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=dmccr@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mbligh@aracnet.com \
--cc=taka@valinux.co.jp \
--cc=tony.luck@intel.com \
--cc=wli@holomorphy.com \
/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