From: Ian Kent <ikent@redhat.com>
To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, willy@infradead.org
Cc: onestero@redhat.com, ebiederm@redhat.com,
Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v3 0/5] proc: improve root readdir latency with many threads
Date: Mon, 12 Dec 2022 10:05:26 +0800 [thread overview]
Message-ID: <2d8ac4c9-abeb-6a36-6c96-b14a5a0a2a31@redhat.com> (raw)
In-Reply-To: <20221202171620.509140-1-bfoster@redhat.com>
On 3/12/22 01:16, Brian Foster wrote:
> Hi all,
>
> Here's v3 of the /proc readdir optimization patches. See v1 for the full
> introductary cover letter.
>
> Most of the feedback received to this point has been around switching
> the pid code over to use the xarray api instead of the idr. Matt Wilcox
> posted most of the code to do that. I cleaned it up a bit and posted a
> standalone series for that here [1], but didn't receive any feedback.
> Patches 1-3 of this series are essentially a repost of [1].
>
> Patches 4-5 are otherwise mostly the same as v2 outside of switching
> over to use the xarray bits instead of the idr/radix-tree.
>
> Thoughts, reviews, flames appreciated.
It looks like there's not much happens with this change so far.
Mathew, could we at least include this in linux-next, to see if
there is anything obvious to worry about since we are fiddling
with the pid numbering ... is there anything we need to do
differently for these to be included in next?
Ian
>
> Brian
>
> [1] https://lore.kernel.org/linux-mm/20220715113349.831370-1-bfoster@redhat.com/
>
> v3:
> - Drop radix-tree fixups.
> - Convert pid idr usage to xarray.
> - Replace tgid radix-tree tag set/lookup to use xarray mark.
> v2: https://lore.kernel.org/linux-fsdevel/20220711135237.173667-1-bfoster@redhat.com/
> - Clean up idr helpers to be more generic.
> - Use ->idr_base properly.
> - Lift tgid iteration helper into pid.c to abstract tag logic from
> users.
> v1: https://lore.kernel.org/linux-fsdevel/20220614180949.102914-1-bfoster@redhat.com/
>
> Brian Foster (5):
> pid: replace pidmap_lock with xarray lock
> pid: split cyclic id allocation cursor from idr
> pid: switch pid_namespace from idr to xarray
> pid: mark pids associated with group leader tasks
> procfs: use efficient tgid pid search on root readdir
>
> arch/powerpc/platforms/cell/spufs/sched.c | 2 +-
> fs/proc/base.c | 17 +--
> fs/proc/loadavg.c | 2 +-
> include/linux/pid.h | 3 +-
> include/linux/pid_namespace.h | 9 +-
> include/linux/threads.h | 2 +-
> init/main.c | 3 +-
> kernel/fork.c | 2 +-
> kernel/pid.c | 177 +++++++++++++---------
> kernel/pid_namespace.c | 23 ++-
> 10 files changed, 132 insertions(+), 108 deletions(-)
>
prev parent reply other threads:[~2022-12-12 2:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:16 Brian Foster
2022-12-02 17:16 ` [PATCH v3 1/5] pid: replace pidmap_lock with xarray lock Brian Foster
2022-12-12 1:44 ` Ian Kent
2022-12-02 17:16 ` [PATCH v3 2/5] pid: split cyclic id allocation cursor from idr Brian Foster
2022-12-12 1:45 ` Ian Kent
2022-12-02 17:16 ` [PATCH v3 3/5] pid: switch pid_namespace from idr to xarray Brian Foster
2022-12-12 1:47 ` Ian Kent
2022-12-02 17:16 ` [PATCH v3 4/5] pid: mark pids associated with group leader tasks Brian Foster
2022-12-12 1:51 ` Ian Kent
2022-12-13 2:00 ` kernel test robot
2022-12-02 17:16 ` [PATCH v3 5/5] procfs: use efficient tgid pid search on root readdir Brian Foster
2022-12-12 1:58 ` Ian Kent
2022-12-12 2:05 ` Ian Kent [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=2d8ac4c9-abeb-6a36-6c96-b14a5a0a2a31@redhat.com \
--to=ikent@redhat.com \
--cc=bfoster@redhat.com \
--cc=ebiederm@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=onestero@redhat.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox