From: "Ober, Frank" <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>,
Cc: "Rajendiran, Swetha" <email@example.com>,
"Liang, Mark" <firstname.lastname@example.org>,
"Derrick, Jonathan" <email@example.com>
Subject: Polled io for Linux kernel 5.x
Date: Thu, 19 Dec 2019 19:25:51 +0000 [thread overview]
Message-ID: <SN6PR11MB2669E7A65DD0AD9DC65A67C58B520@SN6PR11MB2669.namprd11.prod.outlook.com> (raw)
Hi block/nvme communities,
On 4.x kernels we used to be able to do:
# echo 1 > /sys/block/nvme0n1/queue/io_poll
And then run a polled_io job in fio with pvsync2 as our ioengine, with the hipri flag set. This is actually how we test the very best SSDs that depend on 3D xpoint media.
On 5.x kernels we see the following error trying to write the device settings>>>
-bash: echo: write error: Invalid argument
We can reload the entire nvme module with nvme poll_queues but this is not well explained or written up anywhere? Or sorry "not found"?
This is verifiable on 5.3, 5.4 kernels with fio 3.16 builds.
What is the background on what has changed because Jens wrote this note back in 2015, which did work in the 4.x kernel era.
But now things have changed, and there is not a new lwn article that has replaced the one here:
More documentation can be found here on the confusion that exists today is here: https://stackoverflow.com/questions/55223883/echo-write-error-invalid-argument-while-setting-io-poll-for-nvme-ssd/
Can a new LWN article be written around design decisions, usage of these poll_queues?
How come we cannot have a device/controller level setup of polled io today in 5.x kernels, all that exists is module based?
linux-nvme mailing list
next reply other threads:[~2019-12-19 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 19:25 Ober, Frank [this message]
2019-12-19 20:52 ` Polled io for Linux kernel 5.x Keith Busch
2019-12-19 21:59 ` Ober, Frank
2019-12-20 21:20 ` Keith Busch
2019-12-31 19:06 ` Ober, Frank
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).