Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Dan Williams" <dan.j.williams@gmail.com>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>,
	Neil Brown <neilb@suse.de>
Subject: Re: raid 5 read performance
Date: Sat, 5 Aug 2006 10:31:39 -0700	[thread overview]
Message-ID: <e9c3a7c20608051031v2e82c118sd08f7f9cddcca9ce@mail.gmail.com> (raw)
In-Reply-To: <5d96567b0606090850q6185e6a0u8b16860b4f826d4f@mail.gmail.com>

> Neil hello
>
> Sorry for the delay. too many things to do.
>
> I have implemented all said in :
> http://www.spinics.net/lists/raid/msg11838.html
>
> As always I have some questions:
>
> 1.  mergeable_bvec
>      I did not understand first i must admit. now i do not see how it
> differs from the
>      one of raid0.  so i  actually copied it and renamed it.
>
> 2. statistics.
>     i have added md statistics since the code does not reach the
> statics in make_request.
>     it returns from make_request before that.
>
> 3. i have added the new retry list called toread_aligned to raid5_conf_t .
>     hope this is correct.
>
> 4.  your instructions are to add a failed bio to sh, but it does not
> say to handle it directly.
>     i have tried it and something is missing here. raid5d handle
> stripes only if  conf->handle_list is not empty. i added handle_stripe
> and and release_stripe of my own.
>    this way i managed to get from the completion routine:
>    "R5: read error corrected!! " message . ( i have tested by failing
> a ram disk ).
>
>
> 5. I am going to test the non common path heavily before submitting
> you the patch ( on real disks  and use  several file systems and
> several chunk sizes).
>  It is quite a big patch so I need to know which kernel do you want me
> to use ? i am using poor 2.6.15.
>
> I thank you
> --
> Raz
Hi Raz,

What is the status of this patch?  Anything I can help out with, like
testing or forward porting to the latest kernel?

Thanks,

Dan

  parent reply	other threads:[~2006-08-05 17:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 15:50 raid 5 read performance Raz Ben-Jehuda(caro)
2006-06-09 22:59 ` Neil Brown
2006-08-05 17:31 ` Dan Williams [this message]
     [not found]   ` <5d96567b0608051456y795d1930la3d469174f221821@mail.gmail.com>
2006-08-05 22:38     ` Dan Williams
  -- strict thread matches above, loose matches on Subject: below --
2009-09-10 20:07 Raid 5 Read performance Koti
2009-09-10 20:17 ` Majed B.
     [not found]   ` <918883.43112.qm@web94815.mail.in2.yahoo.com>
2009-09-11 18:22     ` Majed B.
2006-05-21  9:10 raid 5 read performance Raz Ben-Jehuda(caro)
2006-05-21  9:17 ` Neil Brown
2006-05-21 17:19   ` Dan Williams
2006-05-21 22:38     ` Neil Brown
2006-10-20 22:16   ` Stephan van Hienen
2006-10-23  4:15     ` 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=e9c3a7c20608051031v2e82c118sd08f7f9cddcca9ce@mail.gmail.com \
    --to=dan.j.williams@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=raziebe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox