linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "Keld Jørn Simonsen" <keld@dkuug.dk>, linux-raid@vger.kernel.org
Subject: Re: recommendations for stripe/chunk size
Date: Wed, 06 Feb 2008 17:37:18 -0500	[thread overview]
Message-ID: <47AA369E.2090501@tmr.com> (raw)
In-Reply-To: <20080206202536.3316124D1D@gemini.denx.de>

Wolfgang Denk wrote:
> In message <47AA08E7.5000801@tmr.com> you wrote:
>   
>>> I actually  think the kernel should operate with block sizes
>>> like this and not wth 4 kiB blocks. It is the readahead and the elevator
>>> algorithms that save us from randomly reading 4 kb a time.
>>>
>>>   
>>>       
>> Exactly, and nothing save a R-A-RW cycle if the write is a partial chunk.
>>     
>
> Indeed kernel page size is an important factor in such optimizations.
> But you have to keep in mind that this is mostly efficient for (very)
> large strictly sequential I/O operations only -  actual  file  system
> traffic may be *very* different.
>
>   
That was actually what I meant by page size, that of the file system 
rather than the memory, ie. the "block size" typically used for writes. 
Or multiples thereof, obviously.
> We implemented the option to select kernel page sizes of  4,  16,  64
> and  256  kB for some PowerPC systems (440SPe, to be precise). A nice
> graphics of the effect can be found here:
>
> https://www.amcc.com/MyAMCC/retrieveDocument/PowerPC/440SPe/RAIDinLinux_PB_0529a.pdf
>
>   
I started that online and pulled a download to print, very neat stuff. 
Thanks for the link.
> Best regards,
>
> Wolfgang Denk
>
>   


-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-02-06 22:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 18:24 recommendations for stripe/chunk size Keld Jørn Simonsen
2008-02-05 19:19 ` Justin Piszcz
2008-02-06 19:22 ` Bill Davidsen
2008-02-06 20:25   ` Wolfgang Denk
2008-02-06 22:37     ` Bill Davidsen [this message]
2008-02-07  0:31     ` Keld Jørn Simonsen
2008-02-07  5:40       ` Iustin Pop
2008-02-07  9:58         ` Keld Jørn Simonsen
2008-02-07  5:51       ` Neil Brown
2008-02-07  5:46     ` Neil Brown
2008-02-07  8:49       ` Wolfgang Denk
2008-02-07  5:31   ` Neil Brown

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=47AA369E.2090501@tmr.com \
    --to=davidsen@tmr.com \
    --cc=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=wd@denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).