From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@gmail.com>
Cc: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: raid 5 read performance
Date: Mon, 22 May 2006 08:38:43 +1000 [thread overview]
Message-ID: <17520.60403.55872.255838@cse.unsw.edu.au> (raw)
In-Reply-To: message from Dan Williams on Sunday May 21
On Sunday May 21, dan.j.williams@gmail.com wrote:
> > Please read
> >
> > http://www.spinics.net/lists/raid/msg11838.html
> >
> > and ask if you have further questions.
> >
> Does this implementation also need to do delayed updates to the stripe
> cache? I.e. we bypass the cache and get the requester the data it
> needs but then schedule that data to also be copied into the cache by
> the work queue. The thinking being to reduce the read penalties
> associated with subsequent writes to the stripe.
>
I doubt that would be worth the effort. I don't think data lives very
long in the stripe cache, and so a lot of the copying would be wasted.
Also, I gather that modern drives have a reasonable cache and if data
was read recently for a read, then reading it again for a write might
be very quick.
I think the gains you get on the read side will more than offset any
small loss on the write side.
NeilBrown
next prev parent reply other threads:[~2006-05-21 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-10-20 22:16 ` Stephan van Hienen
2006-10-23 4:15 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 15:50 Raz Ben-Jehuda(caro)
2006-06-09 22:59 ` Neil Brown
2006-08-05 17:31 ` Dan Williams
[not found] ` <5d96567b0608051456y795d1930la3d469174f221821@mail.gmail.com>
2006-08-05 22:38 ` Dan Williams
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.
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=17520.60403.55872.255838@cse.unsw.edu.au \
--to=neilb@suse.de \
--cc=dan.j.williams@gmail.com \
--cc=linux-raid@vger.kernel.org \
--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