From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [RFC] buddy allocator without bitmap(2) [0/3]
Date: Wed, 01 Sep 2004 08:53:04 +0900 [thread overview]
Message-ID: <41350F60.40608@jp.fujitsu.com> (raw)
In-Reply-To: <20040831162408.3718c83e.akpm@osdl.org>
Andrew Morton wrote:
> Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
>>Because I had to record some information about shape of mem_map, I used PG_xxx bit.
>>1 bit is maybe minimum consumption.
>
>
> The point is that we're running out of bits in page.flags.
>
yes.
> You should be able to reuse an existing bit for this application. PG_lock would suit.
Hmm... PG_buddyend pages in the top of mem_map can be allocated and used as normal pages
,which can be used for Disk I/O.
If I make them as victims to buddy allocator and don't allow to use them,
I can reuse an existing bit.
I'll consider more.
--Kame
WARNING: multiple messages have this Message-ID (diff)
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [RFC] buddy allocator without bitmap(2) [0/3]
Date: Wed, 01 Sep 2004 08:53:04 +0900 [thread overview]
Message-ID: <41350F60.40608@jp.fujitsu.com> (raw)
In-Reply-To: <20040831162408.3718c83e.akpm@osdl.org>
Andrew Morton wrote:
> Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
>>Because I had to record some information about shape of mem_map, I used PG_xxx bit.
>>1 bit is maybe minimum consumption.
>
>
> The point is that we're running out of bits in page.flags.
>
yes.
> You should be able to reuse an existing bit for this application. PG_lock would suit.
Hmm... PG_buddyend pages in the top of mem_map can be allocated and used as normal pages
,which can be used for Disk I/O.
If I make them as victims to buddy allocator and don't allow to use them,
I can reuse an existing bit.
I'll consider more.
--Kame
--
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-31 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 10:36 [RFC] buddy allocator without bitmap(2) [0/3] Hiroyuki KAMEZAWA
2004-08-31 10:36 ` Hiroyuki KAMEZAWA
2004-08-31 16:26 ` Dave Hansen
2004-08-31 16:26 ` Dave Hansen
2004-08-31 22:44 ` [Lhms-devel] " Hiroyuki KAMEZAWA
2004-08-31 22:44 ` Hiroyuki KAMEZAWA
2004-08-31 23:24 ` Andrew Morton
2004-08-31 23:24 ` Andrew Morton
2004-08-31 23:53 ` Hiroyuki KAMEZAWA [this message]
2004-08-31 23:53 ` 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=41350F60.40608@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--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.