From: Brian Foster <bfoster@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ikent@redhat.com, onestero@redhat.com, willy@infradead.org
Subject: [PATCH v2 0/4] proc: improve root readdir latency with many threads
Date: Mon, 11 Jul 2022 09:52:33 -0400 [thread overview]
Message-ID: <20220711135237.173667-1-bfoster@redhat.com> (raw)
Hi all,
Here's v2 of the /proc readdir optimization patches. See v1 for the full
introductary cover letter.
The refactoring in v2 adds a bit more to the idr code, but it remains
trivial with respect to eventual xarray (tag -> mark) conversion. On
that topic, I'm still looking for some feedback in the v1 thread [1] on
the prospective approach...
Brian
[1] https://lore.kernel.org/linux-fsdevel/YrykXim1t71TgdYg@bfoster/
v2:
- 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 (4):
radix-tree: propagate all tags in idr tree
idr: support optional id tagging
pid: tag pids associated with group leader tasks
procfs: use efficient tgid pid search on root readdir
fs/proc/base.c | 17 +----------------
include/linux/idr.h | 26 ++++++++++++++++++++++++++
include/linux/pid.h | 3 ++-
kernel/fork.c | 2 +-
kernel/pid.c | 40 +++++++++++++++++++++++++++++++++++++++-
lib/radix-tree.c | 26 +++++++++++++++-----------
6 files changed, 84 insertions(+), 30 deletions(-)
--
2.35.3
next reply other threads:[~2022-07-11 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:52 Brian Foster [this message]
2022-07-11 13:52 ` [PATCH v2 1/4] radix-tree: propagate all tags in idr tree Brian Foster
2022-07-11 13:52 ` [PATCH v2 2/4] idr: support optional id tagging Brian Foster
2022-07-11 13:52 ` [PATCH v2 3/4] pid: tag pids associated with group leader tasks Brian Foster
2022-07-11 13:52 ` [PATCH v2 4/4] procfs: use efficient tgid pid search on root readdir Brian Foster
2022-07-11 20:19 ` [PATCH v2 0/4] proc: improve root readdir latency with many threads Matthew Wilcox
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=20220711135237.173667-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=ikent@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).