On Saturday October 21, [EMAIL PROTECTED] wrote:
On Sun, 21 May 2006, Neil Brown wrote:
Please read
http://www.spinics.net/lists/raid/msg11838.html
and ask if you have further questions.
Neil,
what is the current status on the slow read performance with 2.6 ?
You mean
On Sun, 21 May 2006, Neil Brown wrote:
Please read
http://www.spinics.net/lists/raid/msg11838.html
and ask if you have further questions.
Neil,
what is the current status on the slow read performance with 2.6 ?
Regards,
Stephan
-
To unsubscribe from this list: send the line
On 8/5/06, Raz Ben-Jehuda(caro) [EMAIL PROTECTED] wrote:
patch is applied by Neil.
I do not know when he going to apply it.
i have applied it on my systems ( on 2.6.15 ) but they are currenly in the
lab and not in production.
Raz.
PS
I must say that it saves lots of cpu cycles.
Did you send
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.
On Friday June 9, [EMAIL PROTECTED] wrote:
Neil hello
Sorry for the delay. too many things to do.
You aren't alone there!
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
Neil hello
I am measuring read performance of two raid5 with 7 sata disks, chunk size 1MB.
when i set the stripe_cache_size to 4096 i get 240 MB/s. IO'ing from
the two raids ended with 270 MB/s.
i have added a code in make_request which passes the raid5 logic in
the case of read.
it looks like
On Sunday May 21, [EMAIL PROTECTED] wrote:
Question :
What is the cost of not walking trough the raid5 code in the
case of READ ?
if i add and error handling code will it be suffice ?
Please read
http://www.spinics.net/lists/raid/msg11838.html
and ask if you have further
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
