From: Ming Lei <ming.lei@redhat.com>
To: Guangwu Zhang <guazhang@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, linux-block@lists.infradead.org,
Yi Zhang <yi.zhang@redhat.com>,
ming.lei@redhat.com
Subject: Re: [PATCH] lib/group_cpus.c: avoid to acquire cpu hotplug lock in group_cpus_evenly
Date: Mon, 14 Aug 2023 10:03:44 +0800 [thread overview]
Message-ID: <ZNmLgBW06NZWUMo1@fedora> (raw)
In-Reply-To: <CAGS2=Ypt3U6AiR77B-WDUMB5atGt9YsuQoEn+PgZVmcH0n8tXg@mail.gmail.com>
Hello Thomas and Guys,
On Fri, Aug 11, 2023 at 06:59:25PM +0800, Guangwu Zhang wrote:
> Hi Ming,
> I don't find any IO block after apply the patch.
>
> Tested-by: Guangwu Zhang <guazhang@redhat.com>
Can you take a look at this fix? And this one solves a couple
of nvme io hang report in case of cpu hotplug & reset involved.
Thanks,
Ming
prev parent reply other threads:[~2023-08-14 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 2:16 [PATCH] lib/group_cpus.c: avoid to acquire cpu hotplug lock in group_cpus_evenly Ming Lei
2023-08-11 10:59 ` Guangwu Zhang
2023-08-14 2:03 ` Ming Lei [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=ZNmLgBW06NZWUMo1@fedora \
--to=ming.lei@redhat.com \
--cc=guazhang@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=yi.zhang@redhat.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