From: keith.busch@intel.com (Keith Busch)
Subject: coalescing in polling mode in 4.9
Date: Mon, 12 Feb 2018 07:53:46 -0700 [thread overview]
Message-ID: <20180212145346.GB16255@localhost.localdomain> (raw)
In-Reply-To: <20180210130817.df352d4336ae0e80ae1755cb@gmail.com>
On Sat, Feb 10, 2018@01:08:17PM -0800, Alex Nln wrote:
> It is quite strange model of IO processing: polling with interrupts.
> Shouldn't these two be mutual exclusive? Why not to disable
> interrupts at all on a queue while polling?
That's a valid point. There are some limitations preventing this at the
moment. The nvme driver currently does not have a way to know the command
it is submitting is intended to be polled, and if it did, we still need
to determine a policy for creating special queue or queues that have
interrupts disabled and how we register these with the block layer.
next prev parent reply other threads:[~2018-02-12 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 8:10 coalescing in polling mode in 4.9 Alex Nln
2018-02-05 0:15 ` Alex Nln
2018-02-05 14:40 ` Sagi Grimberg
2018-02-05 15:02 ` Keith Busch
2018-02-05 15:42 ` Nitesh
2018-02-06 5:39 ` Alex Nln
2018-02-09 22:37 ` Nitesh Shetty
2018-02-10 21:08 ` Alex Nln
2018-02-12 14:53 ` Keith Busch [this message]
2018-02-06 16:29 ` Keith Busch
2018-02-07 8:27 ` Nitesh
2018-02-06 3:55 ` Alex Nln
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=20180212145346.GB16255@localhost.localdomain \
--to=keith.busch@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