From: Shaohua Li <shli@kernel.org>
To: Vladimir Fedorkov <vlad@astellar.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: MD device tinning documentation
Date: Wed, 10 May 2017 09:00:19 -0700 [thread overview]
Message-ID: <20170510160019.6v2bb34kmu6rvr44@kernel.org> (raw)
In-Reply-To: <CA+DJSLwbsUhhK_T+K6YOBX_BLdgRn=qZjz3LUAK92A0_9sL0FQ@mail.gmail.com>
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
prev parent reply other threads:[~2017-05-10 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 10:22 MD device tinning documentation Vladimir Fedorkov
2017-05-10 16:00 ` Shaohua Li [this message]
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=20170510160019.6v2bb34kmu6rvr44@kernel.org \
--to=shli@kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=vlad@astellar.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