All of lore.kernel.org
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH] 2/2 Prezeroing large blocks of pages during allocation Version 4
Date: Tue, 08 Mar 2005 20:40:26 +0900	[thread overview]
Message-ID: <422D8F2A.4010002@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503081012270.30439@skynet>

Mel Gorman wrote:

>>>      
>>>
>>Now, 5bits per  MAX_ORDER pages.
>>I think it is simpler to use "char[]" for representing type of  memory alloc
>>type than bitmap.
>>
>>    
>>
>
>Possibly, but it would also use up that bit more space. That map could be
>condensed to 3 bits but would make it that bit (no pun) more complex and
>difficult to merge. On the other hand, it would be faster to use a char[]
>as it would be an array-index lookup to get a pageblock type rather than a
>number of bit operations.
>
>So, it depends on what people know to be better in general because I have
>not measured it to know for a fact. Is it better to use char[] and use
>array indexes rather than bit operations or is it better to leave it as a
>bitmap and condense it later when things have settled down?
>  
>
Hmm, Okay, I'll wait for condensed version.
BTW, in space consumption/cache view,  does using bitmap have  real 
benefit   ?

Thanks
-- Kame <kamezawa.hiroyu@jp.fujitsu.com>


WARNING: multiple messages have this Message-ID (diff)
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH] 2/2 Prezeroing large blocks of pages during allocation Version 4
Date: Tue, 08 Mar 2005 20:40:26 +0900	[thread overview]
Message-ID: <422D8F2A.4010002@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503081012270.30439@skynet>

Mel Gorman wrote:

>>>      
>>>
>>Now, 5bits per  MAX_ORDER pages.
>>I think it is simpler to use "char[]" for representing type of  memory alloc
>>type than bitmap.
>>
>>    
>>
>
>Possibly, but it would also use up that bit more space. That map could be
>condensed to 3 bits but would make it that bit (no pun) more complex and
>difficult to merge. On the other hand, it would be faster to use a char[]
>as it would be an array-index lookup to get a pageblock type rather than a
>number of bit operations.
>
>So, it depends on what people know to be better in general because I have
>not measured it to know for a fact. Is it better to use char[] and use
>array indexes rather than bit operations or is it better to leave it as a
>bitmap and condense it later when things have settled down?
>  
>
Hmm, Okay, I'll wait for condensed version.
BTW, in space consumption/cache view,  does using bitmap have  real 
benefit   ?

Thanks
-- Kame <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>

  reply	other threads:[~2005-03-08 11:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 19:40 [PATCH] 2/2 Prezeroing large blocks of pages during allocation Version 4 Mel Gorman
2005-03-07 19:40 ` Mel Gorman
2005-03-08  6:14 ` KAMEZAWA Hiroyuki
2005-03-08  6:14   ` KAMEZAWA Hiroyuki
2005-03-08 10:22   ` Mel Gorman
2005-03-08 10:22     ` Mel Gorman
2005-03-08 11:40     ` KAMEZAWA Hiroyuki [this message]
2005-03-08 11:40       ` KAMEZAWA Hiroyuki
2005-03-08 15:04       ` Mel Gorman
2005-03-08 15:04         ` Mel Gorman

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=422D8F2A.4010002@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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.