From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH 0/2] Block: Give option to force io polling
Date: Thu, 31 Mar 2016 14:19:12 -0600 [thread overview]
Message-ID: <1459455554-2794-1-git-send-email-jonathan.derrick@intel.com> (raw)
In 4.6, enabling io polling in direct-io was switched to a per-io flag.
This had an unintended result of giving a significant difference when
doing benchmarks between 4.5 and 4.6, using fio's sync engine.
I was able to regain the performance by getting the pvsync2 engine
working with the new p{read,write}v2 syscalls, but this patchset allows
polling to be tried in the direct-io path with the other syscalls.
Rather than having to convert applications to prwv2 syscalls, users can
enable this knob that let's them see the same performance as they may
have seen in 4.5 when it always polled.
Jon Derrick (2):
block: add queue flag to always poll
block: add forced polling sysfs controls
block/blk-core.c | 8 ++++++++
block/blk-sysfs.c | 38 ++++++++++++++++++++++++++++++++++++++
fs/direct-io.c | 7 ++++++-
include/linux/blkdev.h | 2 ++
4 files changed, 54 insertions(+), 1 deletion(-)
--
2.5.0
next reply other threads:[~2016-03-31 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:19 Jon Derrick [this message]
2016-03-31 20:19 ` [PATCH 1/2] block: add queue flag to always poll Jon Derrick
2016-05-05 21:23 ` Jeff Moyer
2016-05-05 21:34 ` Jon Derrick
2016-03-31 20:19 ` [PATCH 2/2] block: add forced polling sysfs controls Jon Derrick
2016-04-05 12:38 ` [PATCH 0/2] Block: Give option to force io polling Christoph Hellwig
2016-04-05 15:54 ` Keith Busch
2016-04-05 17:27 ` Christoph Hellwig
2016-04-05 18:07 ` Stephen Bates
2016-05-05 19:44 ` Stephen Bates
2016-05-08 9:02 ` hch
2016-05-09 14:53 ` Stephen Bates
2016-05-12 7:08 ` hch
2016-05-12 17:27 ` Stephen Bates
2016-05-12 17:34 ` Derrick, Jonathan
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=1459455554-2794-1-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.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