* MD device tinning documentation
@ 2017-05-08 10:22 Vladimir Fedorkov
2017-05-10 16:00 ` Shaohua Li
0 siblings, 1 reply; 2+ messages in thread
From: Vladimir Fedorkov @ 2017-05-08 10:22 UTC (permalink / raw)
To: linux-raid
Hello there!
I'm running benchmarks and it looks like that md device is only
utilizing single core which it limiting it's performance on concurrent
(4+ threads) writes with 8 SSD drives in software RAID10
Kernel: Linux host 4.10.12-1.el7.elrepo.x86_64 #1 SMP Fri Apr 21
09:58:15 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
Exact numbers are here: http://astellar.com/images/sysbench_rnd_writes.png
Could you please let me know if there is multi-threaded support on MD
devices in 4.x kernels and point me to the documentation (preferred)
or source code which describes tunable parts of /dev/mdXX devices.
Much appreciated!
Thank you!
---
Vlad
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MD device tinning documentation
2017-05-08 10:22 MD device tinning documentation Vladimir Fedorkov
@ 2017-05-10 16:00 ` Shaohua Li
0 siblings, 0 replies; 2+ messages in thread
From: Shaohua Li @ 2017-05-10 16:00 UTC (permalink / raw)
To: Vladimir Fedorkov; +Cc: linux-raid
On Mon, May 08, 2017 at 01:22:53PM +0300, Vladimir Fedorkov wrote:
> Hello there!
>
> I'm running benchmarks and it looks like that md device is only
> utilizing single core which it limiting it's performance on concurrent
> (4+ threads) writes with 8 SSD drives in software RAID10
>
> Kernel: Linux host 4.10.12-1.el7.elrepo.x86_64 #1 SMP Fri Apr 21
> 09:58:15 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> Exact numbers are here: http://astellar.com/images/sysbench_rnd_writes.png
>
> Could you please let me know if there is multi-threaded support on MD
> devices in 4.x kernels and point me to the documentation (preferred)
> or source code which describes tunable parts of /dev/mdXX devices.
There is no knob for tunning. At most time, raid10 directly sends IO to
underlayer disks directly from upperlayer thread, so it's multi-threaded. The
problem is we have some locking issues in the barrier side. Coly improved the
raid1 scalability with a new barrier implementation (fd76863e37fe RAID1: a new
I/O barrier implementation to remove resync window), but raid10 is left behind.
Thanks,
Shaohua
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-10 16:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-08 10:22 MD device tinning documentation Vladimir Fedorkov
2017-05-10 16:00 ` Shaohua Li
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.