From: Jon Derrick <jonathan.derrick@intel.com>
To: linux-block@vger.kernel.org
Cc: Jon Derrick <jonathan.derrick@intel.com>,
"Jens Axboe" <axboe@fb.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"Dan Williams" <dan.j.williams@intel.com>,
"Jeff Moyer" <jmoyer@redhat.com>,
"Stephen Bates" <stephen.bates@microsemi.com>,
"Keith Busch" <keith.busch@intel.com>,
linux-nvme@lists.infradead.org,
"Christoph Hellwig" <hch@infradead.org>
Subject: [RFC 0/2] Support for high-priority block device flag
Date: Thu, 12 May 2016 11:43:04 -0600 [thread overview]
Message-ID: <1463074986-3070-1-git-send-email-jonathan.derrick@intel.com> (raw)
This set intends to recreate block polling (now HIPRI) behavior that was
present in 4.5, where all IO on a queue could be selected to use
block polling behavior. The set allows a block device file to subscribe
to block polling on a block device granularity, rather than a per-queue
granularity.
There have been few-to-no arguments in support of the per-queue,
always-poll functionality that 4.5 offered, moreso in favor of enabling
polling on the entire block device (or indivual IOs as 4.6 offers).
I've been made aware that streams and ioprio may supercede this
functionality in the future, but I'm hoping this is an acceptable
stopgap in the meantime.
This set applies against 4.6-rc7 as well as Jens' for-4.7/core
(I've also been made aware that it may not apply cleanly to 4.7 after
several DAX changes)
Jon Derrick (2):
block: allow other bd i_node flags when DAX is disabled
block: Introduce S_HIPRI inode flag
block/ioctl.c | 33 +++++++++++++++++++++++++++++++++
fs/block_dev.c | 5 ++++-
include/linux/fs.h | 2 ++
include/uapi/linux/fs.h | 2 ++
4 files changed, 41 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2016-05-12 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 17:43 Jon Derrick [this message]
2016-05-12 17:43 ` [RFC 1/2] block: allow other bd i_node flags when DAX is disabled Jon Derrick
2016-05-13 9:18 ` Carlos Maiolino
2016-05-13 13:25 ` Dan Williams
2016-05-13 17:33 ` Jeff Moyer
2016-05-13 17:53 ` Dan Williams
2016-05-13 18:01 ` Jon Derrick
2016-05-12 17:43 ` [RFC 2/2] block: Introduce S_HIPRI inode flag Jon Derrick
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=1463074986-3070-1-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=stephen.bates@microsemi.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).