From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@fb.com>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Cc: Stefan Haberland <sth@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] blk-mq: support physical CPU hotplug
Date: Fri, 12 Jan 2018 09:12:24 +0100 [thread overview]
Message-ID: <64c62449-27d2-a0a1-c7db-d2d08a3eb893@de.ibm.com> (raw)
In-Reply-To: <20180112025306.28004-1-ming.lei@redhat.com>
I think we also need cc stable for this. The bug was introduced with
commit 4b855ad37194f7bdbb200ce7a1c7051fecb56a08 upstream.
("blk-mq: Create hctx for each present CPU")
and that was even backported into 4.12 stable.
On 01/12/2018 03:53 AM, Ming Lei wrote:
> Hi,
>
> This two patches support physical CPU hotplug, so that we can make blk-mq
> scale well when new physical CPU is added or removed, and this use case
> is normal for VM world.
>
> Also this patchset fixes the following warning reported by Christian
> Borntraeger:
>
> https://marc.info/?l=linux-block&m=151092973417143&w=2
>
> Christoph Hellwig (2):
> genirq/affinity: assign vectors to all possible CPUs
> blk-mq: simplify queue mapping & schedule with each possisble CPU
>
> block/blk-mq.c | 19 ++++++++-----------
> kernel/irq/affinity.c | 30 +++++++++++++++---------------
> 2 files changed, 23 insertions(+), 26 deletions(-)
>
next prev parent reply other threads:[~2018-01-12 8:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 2:53 [PATCH 0/2] blk-mq: support physical CPU hotplug Ming Lei
2018-01-12 2:53 ` [PATCH 1/2] genirq/affinity: assign vectors to all possible CPUs Ming Lei
2018-01-12 19:35 ` Thomas Gleixner
2018-01-12 2:53 ` [PATCH 2/2] blk-mq: simplify queue mapping & schedule with each possisble CPU Ming Lei
2018-01-16 10:00 ` Stefan Haberland
2018-01-16 10:12 ` jianchao.wang
2018-01-16 12:10 ` Ming Lei
2018-01-16 14:31 ` jianchao.wang
2018-01-16 15:32 ` Ming Lei
2018-01-17 2:56 ` jianchao.wang
2018-01-17 3:52 ` Ming Lei
2018-01-17 5:24 ` jianchao.wang
2018-01-17 6:22 ` Ming Lei
2018-01-17 8:09 ` jianchao.wang
2018-01-17 9:57 ` Ming Lei
2018-01-17 10:07 ` Christian Borntraeger
2018-01-17 10:14 ` Christian Borntraeger
2018-01-17 10:17 ` Ming Lei
2018-01-19 3:05 ` jianchao.wang
2018-01-26 9:31 ` Ming Lei
2018-01-12 8:12 ` Christian Borntraeger [this message]
2018-01-12 10:47 ` [PATCH 0/2] blk-mq: support physical CPU hotplug Johannes Thumshirn
2018-01-12 18:02 ` Jens Axboe
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=64c62449-27d2-a0a1-c7db-d2d08a3eb893@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=sth@linux.vnet.ibm.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).