From: Oleg Nesterov <oleg@redhat.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] exit: combine work under lock in synchronize_group_exit() and coredump_task_exit()
Date: Wed, 19 Mar 2025 21:11:01 +0100 [thread overview]
Message-ID: <20250319201100.GH26879@redhat.com> (raw)
In-Reply-To: <20250319195436.1864415-1-mjguzik@gmail.com>
On 03/19, Mateusz Guzik wrote:
>
> This reduces single-threaded overhead as it avoids one lock+irq trip on
> exit.
>
> It also improves scalability of spawning and killing threads within one
> process (just shy of 5% when doing it on 24 cores on my test jig).
>
> Both routines are moved below kcov and kmsan exit, which should be
> harmless.
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2025-03-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:54 [PATCH v3] exit: combine work under lock in synchronize_group_exit() and coredump_task_exit() Mateusz Guzik
2025-03-19 20:11 ` Oleg Nesterov [this message]
2025-04-01 13:05 ` Mateusz Guzik
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=20250319201100.GH26879@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.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