public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "NeilBrown" <neilb@suse.de>
To: for.poige+linux@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: HugePages for MD's caches -- can this be done in modern kernel?
Date: Sat, 7 Feb 2009 07:16:11 +1100 (EST)	[thread overview]
Message-ID: <39ad4724d7dd3856cec91dc908cd2a7b.squirrel@neil.brown.name> (raw)
In-Reply-To: <43d009740902061127p1a8073ax231877c8ed3eeda9@mail.gmail.com>

On Sat, February 7, 2009 6:27 am, Igor Podlesny wrote:
> 2009/2/7 NeilBrown <neilb@suse.de>:
>> On Sat, February 7, 2009 5:08 am, Igor Podlesny wrote:
>>>    Hi!
>>>
>>>    $(Subj). :-)
>>>
>>>    P. S. Also, I deem there lots of structures in kernel that could
>>> benefit
>>> from using HugePages. But this probably a q-n for another kernel list.
>>
>> I have only a vague idea what HugePages are and it is not at all clear
>> to
>> me why you would want to use them for the MD cache.   I assume you are
>>
> 	HugePages requires less TBL entries so they better fit for large
> buffers, as far as I understand.
>
> 	http://unixfoo.blogspot.com/2007/10/hugepages.html
> 	http://linux-mm.org/HugePagesArticles
>
>> talking about MD/RAID456 as that is the only place we use a cache.
>>
> 	Yeah, "stripe_cache_size" setting.
>>
>> Maybe if you could explain what you are thinking....
>>
> 	Yeah, hope this would suffice.

Not really, no.
md does not use "large buffers",  Just lots of little buffers.

NeilBrown


      reply	other threads:[~2009-02-06 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43d009740902061008p968268bj30a03c6f97139bbe@mail.gmail.com>
2009-02-06 18:11 ` HugePages for MD's caches -- can this be done in modern kernel? Igor Podlesny
     [not found] ` <c39d1fabb5aef8e2ed5158ad59802cf1.squirrel@neil.brown.name>
2009-02-06 19:27   ` Igor Podlesny
2009-02-06 20:16     ` NeilBrown [this message]

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=39ad4724d7dd3856cec91dc908cd2a7b.squirrel@neil.brown.name \
    --to=neilb@suse.de \
    --cc=for.poige+linux@gmail.com \
    --cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox