From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Hirokazu Takahashi <taka@valinux.co.jp>,
linux-mm@kvack.org, lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [RFC] free_area[] bitmap elimination [0/3]
Date: Sat, 21 Aug 2004 15:10:54 +0900 [thread overview]
Message-ID: <4126E76E.2050403@jp.fujitsu.com> (raw)
In-Reply-To: <20040821053735.GV11200@holomorphy.com>
Hi,
William Lee Irwin III wrote:
> William Lee Irwin III wrote:
>
>>>In __free_pages_bulk() changing BUG_ON(bad_range(zone, buddy1)) to
>>>if (bad_range(zone, buddy1)) break; should fix this. The start of
>>>the zone must be aligned to MAX_ORDER so buddy2 doesn't need checks.
>>>It may be worthwhile to make a distinction the bounds checks and the
>>>zone check and to BUG_ON() the zone check in isolation and not repeat
>>>the bounds check for the validity check.
>
>
> On Sat, Aug 21, 2004 at 02:37:56PM +0900, Hiroyuki KAMEZAWA wrote:
>
>>Okay, I understand several BUG_ON() are needless.
>>I'll be more carefull to recognize what is checked.
>
>
> It's not that it's needless, it's that beforehand the bitmap rounding
> up to an even number ensured the __test_and_change_bit() check would
> prevent the bounds check from ever failing, but after the bitmap is
> eliminated, the bounds check is needed to see if we're even examining
> a valid page structure for whether the page can be merged.
>
>
Oh, I said these 2 lines are needless ;) ,sorry for my vagueness.
buddy2 = base + page_idx;
(*) BUG_ON(bad_range(zone, buddy1));
(*) BUG_ON(bad_range(zone, buddy2));
I understand a test before accessing "buddy1" is necessary.
But as I mentioned in other mail, I'm afraid of memory hole in zone.
This cannot be detected by simple range check.
Is this special case of IA64 ? (I don't know other archs than i386 and IA64)
I think
+ if (!pfn_valid(buddy1))
+ break;
will work enough if pfn_valid() works correctly fot zone with hole.
If ZONE is not MAX_ORDER aligned,
if (bad_range(zone,buddy1))
break;
will be needed too.
-- KAME
--
--the clue is these footmarks leading to the door.--
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
--
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-08-21 6:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 2:31 [RFC] free_area[] bitmap elimination [0/3] Hiroyuki KAMEZAWA
2004-08-21 2:55 ` William Lee Irwin III
2004-08-21 4:56 ` [Lhms-devel] " Hirokazu Takahashi
2004-08-21 5:21 ` William Lee Irwin III
2004-08-21 5:37 ` Hiroyuki KAMEZAWA
2004-08-21 5:37 ` William Lee Irwin III
2004-08-21 6:10 ` Hiroyuki KAMEZAWA [this message]
2004-08-21 17:48 ` William Lee Irwin III
2004-08-21 5:00 ` Hiroyuki KAMEZAWA
2004-08-21 5:01 ` [Lhms-devel] " Hirokazu Takahashi
2004-08-21 5:26 ` Hiroyuki KAMEZAWA
2004-08-21 5:01 ` William Lee Irwin III
2004-08-21 9:43 ` Nigel Cunningham
2004-08-23 14:36 ` [Lhms-devel] " Dave Hansen
2004-08-23 15:00 ` Dave Hansen
2004-08-24 0:07 ` [Lhms-devel] " Hiroyuki KAMEZAWA
2004-08-24 0:00 ` [Lhms-devel] " Hiroyuki KAMEZAWA
2004-08-24 2:28 ` Hirokazu Takahashi
2004-08-24 2:49 ` Dave Hansen
2004-08-24 3:31 ` Hiroyuki KAMEZAWA
2004-08-23 15:43 ` Dave Hansen
2004-08-24 0:15 ` Hiroyuki KAMEZAWA
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=4126E76E.2050403@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
--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 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.