Thread (17 messages) 17 messages, 3 authors, 2012-05-09

Re: [RFC 1/2] MD: raid5 trim support

From: Dan Williams <hidden>
Date: 2012-05-08 15:52:07

On Tue, May 8, 2012 at 3:16 AM, Shaohua Li [off-list ref] wrote:
quoted
quoted
Writing the parity disk is worse. Discard is to improve the garbage
collection
of SSD firmware, so improve later write performance. While write is bad for
SSD, because SSD can be wear leveling out with extra write and also write
increases garbage collection overhead. So the result of small
discard is data
disk garbage collection is improved but parity disk gets worse and
parity disk
gets fast to end of its life, which doesn't make sense. This is even
worse when
the parity is distributed.
Neil,
Any comments about the patches?
ping!
So, are we still in the position of needing to degrade individual
stripes to support trim?  Is there any benefit to making this a
temporary condition?  I.e. trim large ranges, including the parity
disk, and then once all the trim sequences have coalesced resync the
stripes that remain only partially trimmed?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help