From: Dave Hansen <haveblue@us.ibm.com>
To: Matthew E Tolentino <matthew.e.tolentino@intel.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.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>
Subject: Re: [PATCH] no buddy bitmap patch : intro and includes [0/2]
Date: Thu, 07 Oct 2004 08:39:38 -0700 [thread overview]
Message-ID: <1097163578.3625.43.camel@localhost> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB007ED31D6@fmsmsx406.amr.corp.intel.com>
On Thu, 2004-10-07 at 08:03, Tolentino, Matthew E wrote:
> >> Followings are patches for removing bitmaps from buddy=20
> >allocator, against 2.6.9-rc3.
> >> I think this version is much clearer than ones I posted a month ago.
> >...
> >> If there is unclear point, please tell me.
> >
> >What was the purpose behind this, again? Sorry, has been too long since
> >I last looked.
>
> For one, it avoids the otherwise requisite resizing of the bitmaps=20
> during memory hotplug operations...
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.
-- Dave
--
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-07 15:39 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 [this message]
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
-- 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=1097163578.3625.43.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.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