All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: stan@hardwarefreak.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Speeding up chunk size change?
Date: Sun, 04 Mar 2012 13:27:44 +1100	[thread overview]
Message-ID: <4F52D320.4080206@crc.id.au> (raw)
In-Reply-To: <4F52D259.4050907@hardwarefreak.com>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On 4/03/2012 1:24 PM, Stan Hoeppner wrote:
> On 3/3/2012 6:56 PM, Steven Haigh wrote:
>> On 4/03/2012 8:42 AM, Stan Hoeppner wrote:
> [snip]
>>>> blockdev --setra 8192 /dev/sd[abcdefg]
>>>
>>> Read-ahead is per file descriptor, and occurs at the filesystem level.
>>> The read-ahead value used is that of the device immediately underlying
>>> the filessytem.  So don't bother setting these above.
>>
>> Interesting - I didn't think that was the case for whole disk arrays -
>> but there you go... Learnt something else :)
> [snip]
>>>>           echo 4096>   /sys/block/$i/queue/read_ahead_kb
>>> Eliminate this line ^^^^
>>
>> Any insight into why? I would have thought that this would help -
>> however I'm not quite sure as to the values - as this is much less than
>> one chunk... That also being said, wouldn't it be a good idea to have
>> *some* readahead?
>
> You read the answer up above, and commented on it.  Maybe you didn't
> fully understand?  Or maybe it's because you don't know that these two
> are functionally equivalent?
>
> blockdev --setra X
> echo X>   /sys/block/$i/queue/read_ahead_kb

Ahhh - you're spot on... I didn't think they had the same functionality!

-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4952 bytes --]

  reply	other threads:[~2012-03-04  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 19:36 Speeding up chunk size change? Steven Haigh
2012-03-03 21:42 ` Stan Hoeppner
2012-03-04  0:56   ` Steven Haigh
2012-03-04  2:24     ` Stan Hoeppner
2012-03-04  2:27       ` Steven Haigh [this message]
2012-03-04  2:37         ` Bernd Schubert

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=4F52D320.4080206@crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.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.