From: Kunal Kushwaha <kunal.kushwaha@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Query regarding stripe management in linux md-raid
Date: Sat, 2 May 2009 12:48:18 +0530 [thread overview]
Message-ID: <fbae8f520905020018mc6bb23cw51301052ff164928@mail.gmail.com> (raw)
In-Reply-To: <87zldwjybm.fsf@frosties.localdomain>
Hi Goswin,
My understanding of chunk size is that, it is minimum unit of data
that is used for read/write.
Chunk size defines, amount of data written on one disk after breaking
it in equal no of chunks.
Chunk size = Stripe size / (disks in array - parity disks)
so for raid 5, chunk_size = Stripe_Size / (total_disks -1)
and for raid 6, chunk_size = Stripe_Size / total_disks -2)
and parity is also written in terms of chunk size.
Now considering a case where IO request came for complete 1 stripe, we
need buffer, for 1 stripe, but since we allocated 1 page per chunk,
instead of 64k buffer we have only 4k buffer, So how this is handled?
Thanks & Regards,
Kunal
On Sat, May 2, 2009 at 3:11 AM, Goswin von Brederlow <goswin-v-b@web.de> wrote:
> Kunal Kushwaha <kunal.kushwaha@gmail.com> writes:
>
>> Hi Neil,
>>
>> Thanks for your reply. I am trying to find out problems that I could
>> face later on.
>>
>> On Wed, Apr 29, 2009 at 7:15 AM, Neil Brown <neilb@suse.de> wrote:
>>> On Tuesday April 28, kunal.kushwaha@gmail.com wrote:
>>>> Hi,
>>>>
>>>> I am trying to put Linux raid in Box with 256 MB of RAM. The kernel is
>>>> compiled with non-swappable memory management option. I looked into
>>>> raid5.c and found, it allocates one page for each chunk. I am using 5
>>>> disks for 64k chunk size. considering my kernel is within 30 MB.
>>>
>>> That isn't quite right. It is not 1 page per chunk.
>>> raid5 maintains a stripe cache. Each entry in the cache has one page
>>> per device, and there are 256 entries by default.
>>> So for a 5-disk array, that is 5*256 == 1280 pages or 5MB (plus
>>> overhead).
>>>
>>
>> Sorry I missed to mention about stripe cache. Yes we will be using
>> only 5MB if we
>> consider page size is of 4k.
>>
>> I have one more doubt regarding this. How a page of 4k will be able to
>> store data of
>> 64k( my chunk size if of 64k) ?
>
> A chunk size of 64k does in no way mean all transactions are done in
> 64k chunks.
>
> What effect does chunk size actually do have? Was it just the amount
> of sequential data before the parity is rotated in a raid5/6.
>
> MfG
> Goswin
>
--
Regards,
Kunal Kushwaha
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-02 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 14:02 Query regarding stripe management in linux md-raid Kunal Kushwaha
2009-04-28 23:15 ` Neil Brown
2009-04-29 7:27 ` Kunal Kushwaha
2009-05-01 21:41 ` Goswin von Brederlow
2009-05-02 7:18 ` Kunal Kushwaha [this message]
2009-05-04 17:04 ` Goswin von Brederlow
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=fbae8f520905020018mc6bb23cw51301052ff164928@mail.gmail.com \
--to=kunal.kushwaha@gmail.com \
--cc=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).