Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Kunal Kushwaha <kunal.kushwaha@gmail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	Neil Brown <neilb@suse.de>,
	linux-raid@vger.kernel.org
Subject: Re: Query regarding stripe management in linux md-raid
Date: Mon, 04 May 2009 19:04:04 +0200	[thread overview]
Message-ID: <87y6tclrzv.fsf@frosties.localdomain> (raw)
In-Reply-To: <fbae8f520905020018mc6bb23cw51301052ff164928@mail.gmail.com> (Kunal Kushwaha's message of "Sat, 2 May 2009 12:48:18 +0530")

Kunal Kushwaha <kunal.kushwaha@gmail.com> writes:

> 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?

No. read/write are generaly handled on a page size level, which almost
always means 4k. If you think about it you can easily split a chunk
into 4k bits and handle each one independently.

MfG
        Goswin

      reply	other threads:[~2009-05-04 17:04 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
2009-05-04 17:04         ` Goswin von Brederlow [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=87y6tclrzv.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=kunal.kushwaha@gmail.com \
    --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