From: Gal Ofri <gal.ofri@volumez.com>
To: "Finlayson, James M CIV (USA)" <james.m.finlayson4.civ@mail.mil>
Cc: "'linux-raid@vger.kernel.org'" <linux-raid@vger.kernel.org>
Subject: Re: Can't get RAID5/RAID6 NVMe randomread IOPS - AMD ROME what am I missing?????
Date: Sun, 1 Aug 2021 14:21:07 +0300 [thread overview]
Message-ID: <20210801142107.407b000a@gofri-dell> (raw)
In-Reply-To: <5EAED86C53DED2479E3E145969315A2385841062@UMECHPA7B.easf.csd.disa.mil>
Hey Jim,
Read iops (rand/seq) were addressed in a recent commit:
97ae27252f49 md/raid5: avoid device_lock in read_one_chunk()
https://github.com/torvalds/linux/commit/97ae27252f4962d0fcc38ee1d9f913d817a2024e
It was merged into 5.14, so you can either cherry-pick it or just use a
latest-master kernel.
Sounds like your environment is stronger than the one I used for the
testing, so please do share your benchmark if you manage to surpass the
results described in the commit message.
Cheers,
Gal Ofri,
Volumez (formerly storing.io)
next prev parent reply other threads:[~2021-08-01 11:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 20:32 Can't get RAID5/RAID6 NVMe randomread IOPS - AMD ROME what am I missing????? Finlayson, James M CIV (USA)
2021-07-27 21:52 ` Chris Murphy
2021-07-27 22:42 ` Peter Grandi
2021-07-28 10:31 ` Matt Wallis
2021-07-28 10:43 ` [Non-DoD Source] " Finlayson, James M CIV (USA)
2021-07-29 0:54 ` [Non-DoD Source] " Matt Wallis
2021-07-29 16:35 ` Wols Lists
2021-07-29 18:12 ` Finlayson, James M CIV (USA)
2021-07-29 22:05 ` Finlayson, James M CIV (USA)
2021-07-30 8:28 ` Matt Wallis
2021-07-30 8:45 ` Miao Wang
2021-07-30 9:59 ` Finlayson, James M CIV (USA)
2021-07-30 14:03 ` Doug Ledford
2021-07-30 13:17 ` Peter Grandi
2021-07-30 9:54 ` Finlayson, James M CIV (USA)
2021-08-01 11:21 ` Gal Ofri [this message]
2021-08-03 14:59 ` [Non-DoD Source] " Finlayson, James M CIV (USA)
2021-08-04 9:33 ` Gal Ofri
[not found] ` <AS8PR04MB799205817C4647DAC740DE9A91EA9@AS8PR04MB7992.eurprd04.prod.outlook.com>
[not found] ` <5EAED86C53DED2479E3E145969315A2385856AD0@UMECHPA7B.easf.csd.disa.mil>
[not found] ` <5EAED86C53DED2479E3E145969315A2385856AF7@UMECHPA7B.easf.csd.disa.mil>
2021-08-05 19:52 ` Finlayson, James M CIV (USA)
2021-08-05 20:50 ` Finlayson, James M CIV (USA)
2021-08-05 21:10 ` Finlayson, James M CIV (USA)
2021-08-08 14:43 ` Gal Ofri
2021-08-09 19:01 ` Finlayson, James M CIV (USA)
2021-08-17 21:21 ` Finlayson, James M CIV (USA)
2021-08-18 0:45 ` [Non-DoD Source] " Matt Wallis
2021-08-18 10:20 ` Finlayson, James M CIV (USA)
2021-08-18 19:48 ` Doug Ledford
2021-08-18 19:59 ` Doug Ledford
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=20210801142107.407b000a@gofri-dell \
--to=gal.ofri@volumez.com \
--cc=james.m.finlayson4.civ@mail.mil \
--cc=linux-raid@vger.kernel.org \
/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