From: Johannes Weiner <hannes@saeurebad.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [RFC][patch 0/5] Bootmem fixes
Date: Thu, 17 Apr 2008 12:49:27 +0200 [thread overview]
Message-ID: <87lk3ceoy0.fsf@saeurebad.de> (raw)
In-Reply-To: <20080417183639.7d3831e0.kamezawa.hiroyu@jp.fujitsu.com> (KAMEZAWA Hiroyuki's message of "Thu, 17 Apr 2008 18:36:39 +0900")
Hi,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> On Wed, 16 Apr 2008 13:36:29 +0200
> Johannes Weiner <hannes@saeurebad.de> wrote:
>
>> Hi,
>>
>> here are a bunch of fixes for the bootmem allocator. These are tested
>> on boring x86_32 UMA hardware, but 3 patches only show their effects
>> on multi-node systems, so please review and test.
>>
>> Only the first two patches are real code changes, the others are
>> cleanups.
>>
>> `Node-setup agnostic free_bootmem()' assumes that all bootmem
>> descriptors describe contiguous regions and bdata_list is in ascending
>> order. Yinghai was unsure about this fact, Ingo could you ACK/NAK
>> this?
>>
> Tested on ia64/NUMA box on 2.6.25. seems no problem.
Cool, thanks a lot!
Hannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@saeurebad.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: Re: [RFC][patch 0/5] Bootmem fixes
Date: Thu, 17 Apr 2008 12:49:27 +0200 [thread overview]
Message-ID: <87lk3ceoy0.fsf@saeurebad.de> (raw)
In-Reply-To: <20080417183639.7d3831e0.kamezawa.hiroyu@jp.fujitsu.com> (KAMEZAWA Hiroyuki's message of "Thu, 17 Apr 2008 18:36:39 +0900")
Hi,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> On Wed, 16 Apr 2008 13:36:29 +0200
> Johannes Weiner <hannes@saeurebad.de> wrote:
>
>> Hi,
>>
>> here are a bunch of fixes for the bootmem allocator. These are tested
>> on boring x86_32 UMA hardware, but 3 patches only show their effects
>> on multi-node systems, so please review and test.
>>
>> Only the first two patches are real code changes, the others are
>> cleanups.
>>
>> `Node-setup agnostic free_bootmem()' assumes that all bootmem
>> descriptors describe contiguous regions and bdata_list is in ascending
>> order. Yinghai was unsure about this fact, Ingo could you ACK/NAK
>> this?
>>
> Tested on ia64/NUMA box on 2.6.25. seems no problem.
Cool, thanks a lot!
Hannes
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-17 10:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 11:36 [RFC][patch 0/5] Bootmem fixes Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 11:36 ` [RFC][patch 1/5] mm: Revert "mm: fix boundary checking in free_bootmem_core" Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 17:49 ` Yinghai Lu
2008-04-16 17:49 ` Yinghai Lu
2008-04-16 11:36 ` [RFC][patch 2/5] mm: Node-setup agnostic free_bootmem() Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 17:54 ` Yinghai Lu
2008-04-16 17:54 ` Yinghai Lu
2008-04-16 18:44 ` Yinghai Lu
2008-04-16 18:44 ` Yinghai Lu
2008-04-16 18:48 ` Ingo Molnar
2008-04-16 18:48 ` Ingo Molnar
2008-04-16 19:17 ` Johannes Weiner
2008-04-16 19:17 ` Johannes Weiner
2008-04-18 5:06 ` Yinghai Lu
2008-04-18 5:06 ` Yinghai Lu
2008-04-16 19:19 ` Johannes Weiner
2008-04-16 19:19 ` Johannes Weiner
2008-04-16 11:36 ` [RFC][patch 3/5] mm: Unexport __alloc_bootmem_core() Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 11:36 ` [RFC][patch 4/5] mm: Normalize internal argument passing of bootmem data Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 11:36 ` [RFC][patch 5/5] mm: Move bootmem descriptors definition to a single place Johannes Weiner
2008-04-16 11:36 ` Johannes Weiner
2008-04-16 17:30 ` Ralf Baechle
2008-04-16 17:30 ` Ralf Baechle
2008-04-17 9:36 ` [RFC][patch 0/5] Bootmem fixes KAMEZAWA Hiroyuki
2008-04-17 9:36 ` KAMEZAWA Hiroyuki
2008-04-17 10:49 ` Johannes Weiner [this message]
2008-04-17 10:49 ` Johannes Weiner
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=87lk3ceoy0.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.