linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: ebiederm@xmission.com, oleg@redhat.com, brauner@kernel.org,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/5] reduce tasklist_lock hold time on exit and do some pid cleanup
Date: Thu, 6 Feb 2025 12:14:34 -0500	[thread overview]
Message-ID: <572h7chpl6z5ldizh3oh63olcyb6vyh4k4lq7ozmpwnqybkfxo@qarxk4rdndig> (raw)
In-Reply-To: <20250206164415.450051-1-mjguzik@gmail.com>

* Mateusz Guzik <mjguzik@gmail.com> [250206 11:44]:
> I fixed fat-fingering and touchedup some commit messages. git diff
> between the old and new branch does not show any code changes.


Thanks for doing these changes.

Acked-by: Liam R. Howlett <Liam.Howlett@Oracle.com>

> 
> hopefully we will be done here after this iteration 8->
> 
> old cover letter:
> 
> The clone side contends against exit side in a way which avoidably
> exacerbates the problem by the latter waiting on locks held by the
> former while holding the tasklist_lock.
> 
> Whacking this for both add_device_randomness and pids allocation gives
> me a 15% speed up for thread creation/destruction in a 24-core vm.
> 
> The random patch is worth about 4%.
> 
> The new bottleneck is pidmap_lock itself, with the biggest problem being
> the allocation itself taking the lock *twice*.
> 
> Bench (plop into will-it-scale):
> $ cat tests/threadspawn1.c
> 
> char *testcase_description = "Thread creation and teardown";
> 
> static void *worker(void *arg)
> {
> 	return (NULL);
> }
> 
> void testcase(unsigned long long *iterations, unsigned long nr)
> {
> 	pthread_t thread;
> 	int error;
> 
> 	while (1) {
> 		error = pthread_create(&thread, NULL, worker, NULL);
> 		assert(error == 0);
> 		error = pthread_join(thread, NULL);
> 		assert(error == 0);
> 		(*iterations)++;
> 	}
> }
> 
> v6:
> - expand on the commit message in 3/5 pid: sprinkle tasklist_lock asserts
> - move fat-fingered free_pids call to the right patch
> 
> v5:
> - whack scripts/selinux/genheaders/genheaders which accidentally got in
> - rebased on next-20250205
> 
> v4:
> - justify moving get_pid in the commit message with a one-liner
> - drop the tty unref patch -- it is completely optional and Oleg has his
>   own variant
> - add the ACK by Oleg
> 
> v3:
> - keep procfs flush where it was, instead hoist get_pid outside of the
>   lock
> - make detach_pid et al accept an array argument of pids to populate
> - sprinkle asserts
> - drop irq trips around pidmap_lock
> - move tty unref outside of tasklist_lock
> 
> 
> 
> Mateusz Guzik (5):
>   exit: perform add_device_randomness() without tasklist_lock
>   exit: hoist get_pid() in release_task() outside of tasklist_lock
>   pid: sprinkle tasklist_lock asserts
>   pid: perform free_pid() calls outside of tasklist_lock
>   pid: drop irq disablement around pidmap_lock
> 
>  include/linux/pid.h |  7 ++--
>  kernel/exit.c       | 36 +++++++++++++-------
>  kernel/pid.c        | 82 +++++++++++++++++++++++++--------------------
>  kernel/sys.c        | 14 +++++---
>  4 files changed, 82 insertions(+), 57 deletions(-)
> 
> -- 
> 2.43.0
> 


  parent reply	other threads:[~2025-02-06 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 16:44 Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 1/5] exit: perform add_device_randomness() without tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 2/5] exit: hoist get_pid() in release_task() outside of tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 3/5] pid: sprinkle tasklist_lock asserts Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 4/5] pid: perform free_pid() calls outside of tasklist_lock Mateusz Guzik
2025-02-06 16:44 ` [PATCH v6 5/5] pid: drop irq disablement around pidmap_lock Mateusz Guzik
2025-02-06 17:14 ` Liam R. Howlett [this message]
2025-02-07  9:18 ` [PATCH v6 0/5] reduce tasklist_lock hold time on exit and do some pid cleanup Christian Brauner
2025-02-07  9:42   ` Oleg Nesterov

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=572h7chpl6z5ldizh3oh63olcyb6vyh4k4lq7ozmpwnqybkfxo@qarxk4rdndig \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mjguzik@gmail.com \
    --cc=oleg@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