From: Mike Kravetz <mike.kravetz@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, stable@vger.kernel.org,
songmuchun@bytedance.com, naoya.horiguchi@linux.dev,
mhocko@suse.com, linmiaohe@huawei.com, jthoughton@google.com,
jiaqiyan@google.com, axelrasmussen@google.com
Subject: Re: + hugetlb-optimize-update_and_free_pages_bulk-to-avoid-lock-cycles.patch added to mm-hotfixes-unstable branch
Date: Thu, 13 Jul 2023 11:16:53 -0700 [thread overview]
Message-ID: <20230713181653.GA4424@monkey> (raw)
In-Reply-To: <20230713173444.6B21CC433C8@smtp.kernel.org>
On 07/13/23 10:34, Andrew Morton wrote:
>
> The patch titled
> Subject: hugetlb: optimize update_and_free_pages_bulk to avoid lock cycles
> has been added to the -mm mm-hotfixes-unstable branch. Its filename is
> hugetlb-optimize-update_and_free_pages_bulk-to-avoid-lock-cycles.patch
Muchun pointed out that this patch does not address the issue raised by
Jiaqi Yan. In fact, I accidentally sent the wrong (previous) version of
the patch. I mentioned that while getting ready to send the correct version,
I noticed another race window. I am currently finishing some testing on
that.
Bottom line is that this patch should not move forward.
A new version will be sent and I will attempt to answer your questions about
introducing a performance regression.
Sorry for any confusion,
--
Mike Kravetz
prev parent reply other threads:[~2023-07-13 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 17:34 + hugetlb-optimize-update_and_free_pages_bulk-to-avoid-lock-cycles.patch added to mm-hotfixes-unstable branch Andrew Morton
2023-07-13 18:16 ` Mike Kravetz [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=20230713181653.GA4424@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=naoya.horiguchi@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
/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.