From: "hch@infradead.org" <hch@infradead.org>
To: Stephen Bates <stephen.bates@microsemi.com>
Cc: Jon Derrick <jonathan.derrick@intel.com>,
"axboe@fb.com" <axboe@fb.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"keith.busch@intel.com" <keith.busch@intel.com>,
"hch@infradead.org" <hch@infradead.org>
Subject: Re: [PATCH 0/2] Block: Give option to force io polling
Date: Sun, 8 May 2016 02:02:57 -0700 [thread overview]
Message-ID: <20160508090257.GG15458@infradead.org> (raw)
In-Reply-To: <D87A37E7A4AA544D853031D9A919C70B168FDA58@avsrvexchmbx2.microsemi.net>
On Thu, May 05, 2016 at 07:44:29PM +0000, Stephen Bates wrote:
> I am very interested in seeing this added. There are use cases involving super-low latency (non-NAND based) NVMe devices and they want the fastest possible IO response times for ALL IO to that device. They also have no desire to wait for the new system calls and glibc updates needed to tie their applications into polling or to rewrite their applications to avail of those new calls. I have done some testing on Jon's "big hammer" and it seems to work well for this use case and applied cleanly against v4.6-rc6.
Let's get the driver for those devices merged first, and if you can
provide numbers that it's worth it we can add a tweak to always enable
polling from the driver for those devices.
next prev parent reply other threads:[~2016-05-08 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:19 [PATCH 0/2] Block: Give option to force io polling Jon Derrick
2016-04-05 12:38 ` 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 [this message]
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=20160508090257.GG15458@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=stephen.bates@microsemi.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;
as well as URLs for NNTP newsgroup(s).