From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Matthew Wilcox <willy@linux.intel.com>, Hannes Reinecke <hare@suse.de>
Cc: "lsf@lists.linux-foundation.org" <lsf@lists.linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Lsf] [LSF/MM TOPIC] block-mq issues with FC
Date: Fri, 8 Apr 2016 11:14:24 -0700 [thread overview]
Message-ID: <5707F500.6030206@sandisk.com> (raw)
In-Reply-To: <20160408174006.GI2781@linux.intel.com>
On 04/08/2016 10:40 AM, Matthew Wilcox wrote:
> - Interrupt steering needs to be controlled by block-mq instead of
> the driver. It's pointless to have each driver implement its own
> policies on interrupt steering, irqbalanced remains a source of
> end-user frustration, and block-mq can change the queue<->cpu mapping
> without the driver's knowledge.
I'm looking forward to the day that I will be able to drop my script for
spreading interrupts manually (see also the fifth attachment of
http://thread.gmane.org/gmane.linux.kernel.device-mapper.devel/21312/focus=98409).
Bart.
next prev parent reply other threads:[~2016-04-08 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 11:29 [LSF/MM TOPIC] block-mq issues with FC Hannes Reinecke
2016-04-08 15:11 ` James Bottomley
2016-04-08 15:51 ` [Lsf] " Ewan D. Milne
2016-04-08 16:06 ` James Bottomley
2016-04-08 17:26 ` Bart Van Assche
2016-04-08 17:40 ` Matthew Wilcox
2016-04-08 18:00 ` James Bottomley
2016-04-08 18:08 ` Christoph Hellwig
2016-04-08 18:24 ` James Bottomley
2016-04-08 18:06 ` Keith Busch
2016-04-12 19:16 ` Jens Axboe
2016-04-08 18:14 ` Bart Van Assche [this message]
2016-04-08 19:22 ` Waskiewicz, PJ
2016-04-10 19:02 ` Sagi Grimberg
2016-04-12 19:04 ` Quinn Tran
2016-04-08 18:13 ` Christoph Hellwig
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=5707F500.6030206@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf@lists.linux-foundation.org \
--cc=willy@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.