From: Jim Newsome <jnewsome@torproject.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Christian Brauner <christian@brauner.io>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] do_wait: make PIDTYPE_PID case O(1) instead of O(n)
Date: Fri, 12 Mar 2021 12:39:12 -0600 [thread overview]
Message-ID: <ccfef0d5-c419-0a8d-cf75-9642e9d11f94@torproject.org> (raw)
In-Reply-To: <20210312102207.a347e38db375226a78cc37bf@linux-foundation.org>
On 3/12/21 12:22, Andrew Morton wrote:
>
> Could we please see some performance testing results to permit us to
> evaluate the value of this change?
Sure. I've been doing some ad-hoc measurements with the code below. It
forks 8k children and then waits for them in reverse order (forcing a
full list traversal each time). I'll need to reboot a couple times to
get apples-to-apples measurements on bare metal, though. I'll plan to
run with NUMCHILDREN = 0 -> 8000, by 100.
Does this look like it'd be sufficient, or is there more you'd like to
see? The current form doesn't use ptrace, but I expect the results to be
similar; (maybe more pronounced when tracing threaded children, since
every thread is in the tracee list instead of just the group leaders).
#define NUMCHILDREN 8000
void fork_and_wait() {
pid_t children[NUMCHILDREN];
for (int i = 0; i < NUMCHILDREN; ++i) {
pid_t forkrv = fork();
if (forkrv < 0) {
perror("fork");
exit(1);
}
if (forkrv == 0) {
// child
exit(0);
}
// parent
children[i] = forkrv;
}
for (int i = 0; i < NUMCHILDREN; ++i) {
int wstatus;
if (waitpid(children[NUMCHILDREN - i - 1], &wstatus, 0) < 0) {
perror("waitpid");
exit(1);
}
}
}
next prev parent reply other threads:[~2021-03-12 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 17:38 Jim Newsome
2021-03-12 18:22 ` Andrew Morton
2021-03-12 18:39 ` Jim Newsome [this message]
2021-03-12 18:47 ` Andrew Morton
2021-03-13 2:42 ` Jim Newsome
2021-03-12 20:01 ` Jim Newsome
2021-03-12 20:29 ` Eric W. Biederman
2021-03-12 21:05 ` Jim Newsome
2021-03-12 21:25 ` Eric W. Biederman
2021-03-13 17:25 ` 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=ccfef0d5-c419-0a8d-cf75-9642e9d11f94@torproject.org \
--to=jnewsome@torproject.org \
--cc=akpm@linux-foundation.org \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®