From: Artem Bityutskiy <dedekind1@gmail.com>
To: "hch@lst.de" <hch@lst.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"snitzer@redhat.com" <snitzer@redhat.com>,
"hare@suse.de" <hare@suse.de>, "mroos@linux.ee" <mroos@linux.ee>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"don.brace@microsemi.com" <don.brace@microsemi.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"loberman@redhat.com" <loberman@redhat.com>,
"kashyap.desai@broadcom.com" <kashyap.desai@broadcom.com>,
Jens Axboe <axboe@kernel.dk>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Subject: Re: [PATCH V5 1/5] scsi: hpsa: fix selection of reply queue
Date: Mon, 19 Mar 2018 16:42:09 +0200 [thread overview]
Message-ID: <1521470529.4592.51.camel@gmail.com> (raw)
In-Reply-To: <cf7fd125-f809-cd13-ef56-280acba80f00@kernel.dk>
On Mon, 2018-03-19 at 08:31 -0600, Jens Axboe wrote:
> I'm assuming that Martin will eventually queue this up. But probably
> for 4.17, then we can always flag it for a backport to stable once
> it's been thoroughly tested.
Jens, thanks for reply.
I wonder if folks agree that in this case we should revert
84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
for v4.16.
If this was a minor niche use-case regression the -stable scenario
would probably be OK. But the patch seem to miss the fact that kernel's
"possible CPUs" notion may be way off and side effects are bad.
Christoph, Thomas, what do you think?
Thanks,
Artem.
next prev parent reply other threads:[~2018-03-19 14:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 9:42 [PATCH V5 0/5] SCSI: fix selection of reply(hw) queue Ming Lei
2018-03-13 9:42 ` [PATCH V5 1/5] scsi: hpsa: fix selection of reply queue Ming Lei
2018-03-14 8:57 ` Christoph Hellwig
2018-03-14 15:07 ` Bityutskiy, Artem
2018-03-19 11:48 ` Bityutskiy, Artem
2018-03-19 14:31 ` Jens Axboe
2018-03-19 14:42 ` Artem Bityutskiy [this message]
2018-03-19 14:55 ` Kashyap Desai
2018-03-19 15:26 ` Ming Lei
2018-03-20 3:16 ` Martin K. Petersen
2018-03-13 9:42 ` [PATCH V5 2/5] scsi: megaraid_sas: " Ming Lei
2018-03-13 17:13 ` Kashyap Desai
2018-03-14 8:57 ` Christoph Hellwig
2018-03-14 15:07 ` Artem Bityutskiy
2018-03-13 9:42 ` [PATCH V5 3/5] scsi: introduce force_blk_mq Ming Lei
2018-03-13 9:42 ` [PATCH V5 4/5] scsi: virtio_scsi: fix IO hang caused by irq vector automatic affinity Ming Lei
2018-03-14 8:58 ` Christoph Hellwig
2018-03-13 9:42 ` [PATCH V5 5/5] scsi: virtio_scsi: unify scsi_host_template Ming Lei
2018-03-14 8:58 ` Christoph Hellwig
2018-03-15 3:35 ` [PATCH V5 0/5] SCSI: fix selection of reply(hw) queue Martin K. Petersen
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=1521470529.4592.51.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=don.brace@microsemi.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=mroos@linux.ee \
--cc=pbonzini@redhat.com \
--cc=snitzer@redhat.com \
--cc=tglx@linutronix.de \
/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).