From: Christoph Hellwig <hch@infradead.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: axboe@fb.com, keith.busch@intel.com, hch@infradead.org,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
stephen.bates@microsemi.com
Subject: Re: [PATCH 0/2] Block: Give option to force io polling
Date: Tue, 5 Apr 2016 05:38:32 -0700 [thread overview]
Message-ID: <20160405123832.GA27788@infradead.org> (raw)
In-Reply-To: <1459455554-2794-1-git-send-email-jonathan.derrick@intel.com>
On Thu, Mar 31, 2016 at 02:19:12PM -0600, Jon Derrick wrote:
> 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.
Only if you manually enabled polling beforehand. I really don't see
how this is going to be useful for actual applications vs benchmarks,
so I'll need more convincing arguments.
next prev parent reply other threads:[~2016-04-05 12:38 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 [this message]
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=20160405123832.GA27788@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).