From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
"scameron@beardog.cce.hp.com" <scameron@beardog.cce.hp.com>,
Bart Van Assche <bvanassche@acm.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: respect rq_affinity
Date: Fri, 25 Apr 2014 08:23:45 -0600 [thread overview]
Message-ID: <535A6FF1.6070805@kernel.dk> (raw)
In-Reply-To: <20140425093253.GA18345@infradead.org>
On 04/25/2014 03:32 AM, Christoph Hellwig wrote:
> From: Christoph Hellwig <hch@lst.de>
>
> The blk-mq code is using it's own version of the I/O completion affinity
> tunables, which causes a few issues:
>
> - the rq_affinity sysfs file doesn't work for blk-mq devices, even if it
> still is present, thus breaking existing tuning setups.
> - the rq_affinity = 1 mode, which is the defauly for legacy request based
> drivers isn't implemented at all.
> - blk-mq drivers don't implement any completion affinity with the default
> flag settings.
>
> This patches removes the blk-mq ipi_redirect flag and sysfs file, as well
> as the internal BLK_MQ_F_SHOULD_IPI flag and replaces it with code that
> respects the queue-wide rq_affinity flags and also implements the
> rq_affinity = 1 mode.
>
> This means I/O completion affinity can now only be tuned block-queue wide
> instead of per context, which seems more sensible to me anyway.
Agree, this is a good cleanup, and there's no reason blk-mq needs its
own sysfs file for this.
--
Jens Axboe
prev parent reply other threads:[~2014-04-25 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94D0CD8314A33A4D9D801C0FE68B402956EDDA26@G9W0745.americas.hpqcorp.net>
[not found] ` <53592665.8050406@kernel.dk>
[not found] ` <20140425053018.GA30957@infradead.org>
[not found] ` <94D0CD8314A33A4D9D801C0FE68B402956EDE0D8@G9W0745.americas.hpqcorp.net>
[not found] ` <20140425071659.GA15384@infradead.org>
2014-04-25 9:32 ` [PATCH] blk-mq: respect rq_affinity Christoph Hellwig
2014-04-25 14:23 ` Jens Axboe [this message]
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=535A6FF1.6070805@kernel.dk \
--to=axboe@kernel.dk \
--cc=Elliott@hp.com \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scameron@beardog.cce.hp.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