On Sun, Mar 19 2017, Gandalf Corvotempesta wrote: > Hi to all, > I need some info about stripe_cache_size > > Is that a sort of "writeback" cache? Higher the number, higher the > amount of data to be cached in ram before writing to disks, right? No. All of memory is potentially a write-back cache for all filesystems. the stripe_cache is a write-through cache which holds strips (one page per device) while reading missing blocks and computing parity. When the array is degraded, it is also used to hold the blocks in a strip will calculating the missing data. > > Some questions: > > 1) any upper limit for that value ? Can I set it near 1GB like most > hardware controller? It is currently limited to 32768, for no particularly good reason. Several stripes (so several times 64 with the default chunk size) is good. Many stripes might help very random workloads. > 2) why on my RAID-6 I don't have /sys/block/md0/md/stripe_cache_size ? No idea. I certainly should do. > > As I would like to replace most of our HW raid controller with mdadm, > any suggestion on how to improve RAID-6 speed ? > > Modern CPU aren't an issue, I don't think that double-parity > calculation could create any bottleneck on a modern CPU. > The real advantages of a raid controller are mostly 2: > > 1) the writeback cache (1GB or 2GB) > 2) the ability to automatically replace a disk by hotswapping it. > > Any solution to this ? For the "2", i've tried by configuring the > POLICY in mdadm.conf but new disk is never reconized and I always have > to manually add the new disk to the array. What, precisely, have you tried? Please provide exact contents of config files (i.e mdadm.conf) and exact steps you took and what you expected to happen. NeilBrown > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
signature.asc
Description: PGP signature
