All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Neil Brown <neilb@suse.de>
Cc: Leslie Rhorer <lrhorer@satx.rr.com>,
	'Johannes Truschnigg' <johannes@truschnigg.info>,
	linux-raid@vger.kernel.org
Subject: Re: 3T drives and RAID
Date: Sun, 31 Oct 2010 20:05:27 +0100	[thread overview]
Message-ID: <201010312005.27547.bernd.schubert@fastmail.fm> (raw)
In-Reply-To: <20101031113029.226d9e65@notabene>

On Sunday, October 31, 2010, Neil Brown wrote:
> On Sat, 30 Oct 2010 04:21:16 -0500
> 
> "Leslie Rhorer" <lrhorer@satx.rr.com> wrote:
> > 	Md will automatically treat the oddball drive as if it had .5K
> > 
> > sectors, or does one need to tell ma (or the kernel) to do so?
> 
> You don't need to tell the kernel to do anything special - it should just
> work.
> 
> md/raid5 (and raid6) do all writes as 4K blocks, 4K aligned (as the
> stripe-cache is made of pages which are 4K).  So that fits perfectly with
> the new drives.
> If your filesystem issued a non-aligned read, then it could get down to the
> device as a non-aligned read, but there is little performance penalty for
> reads, only writes.
> And XFS almost certainly does all IO in 4K multiples, so you should be
> fine.
> 
> In short: I can see no reason why it shouldn't work smoothly.

Well, I think alignment on a larger basis is something we need to discuss 
about. I have a modified blkiomon on my disk, which shows IO sizes (will send 
the patches to the corresponding list, once I find the time to finalize it).

On one shell:
bathl:~# dd if=/dev/md5 of=/dev/null bs=1M iflag=direct

On  another shell:

bathl:~# blktrace -d /dev/sdc  -d /dev/sdd -a issue -a complete  -o - \| 
/tmpa/devel/blktrace/blktrace-1.0.1/blkiomon -I10 -h -

sizes histogram (kiB):
           32:   470
          124:  3096
          496:   166


(I modified blkiomon not to print the histogram based on doubled IO sizes, but 
to print multiple of 4K and to skip sizes with zero requests).

Well, I think I need to make an option to print it on the basis of 512B, but 
already the present output shows rather bad IO requests. One thing I have 
learned during my work at DDN is that good performance numbers only can be 
achieved if large IO requests come in. Now a DDN hardware raid is certainly 
not comparable with linux software raid, but if the local disk can do 512KB 
requests and gets that with direct io, linux md should do the same.

The same for a read from sdc:

bathl:~# dd if=/dev/sdc of=/dev/null bs=1M iflag=direct

blktrace -d /dev/sdc  -d /dev/sdd -a issue -a complete  -o - \| 
/tmpa/devel/blktrace/blktrace-1.0.1/blkiomon -I10 -h -

sizes histogram (kiB):
          512:  1874


md5 : active raid10 sdc[0] sdd[1]
      976760832 blocks super 1.2 1024K chunks 2 offset-copies [2/2] [UU]
      bitmap: 0/15 pages [0KB], 32768KB chunk


Cheers,
Bernd




      reply	other threads:[~2010-10-31 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30  3:36 3T drives and RAID Leslie Rhorer
2010-10-30  8:33 ` Johannes Truschnigg
2010-10-30  9:21   ` Leslie Rhorer
2010-10-31 15:30     ` Neil Brown
2010-10-31 19:05       ` Bernd Schubert [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=201010312005.27547.bernd.schubert@fastmail.fm \
    --to=bernd.schubert@fastmail.fm \
    --cc=johannes@truschnigg.info \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    --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 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.