From: Matthew Wilcox <willy@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ikent@redhat.com, onestero@redhat.com
Subject: Re: [PATCH v2 0/4] proc: improve root readdir latency with many threads
Date: Mon, 11 Jul 2022 21:19:42 +0100 [thread overview]
Message-ID: <YsyF3rK1YV57HDM/@casper.infradead.org> (raw)
In-Reply-To: <20220711135237.173667-1-bfoster@redhat.com>
On Mon, Jul 11, 2022 at 09:52:33AM -0400, Brian Foster wrote:
> Hi all,
>
> Here's v2 of the /proc readdir optimization patches. See v1 for the full
> introductary cover letter.
I really don't want to change the radix tree or IDR code. That's why
I did the conversion of the pid code to use the XArray for you.
> 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...
Oh, I missed the last few emails in that thread due to being on holiday.
I'll go back and read/reply to them now.
prev parent reply other threads:[~2022-07-11 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:52 [PATCH v2 0/4] proc: improve root readdir latency with many threads Brian Foster
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 ` Matthew Wilcox [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=YsyF3rK1YV57HDM/@casper.infradead.org \
--to=willy@infradead.org \
--cc=bfoster@redhat.com \
--cc=ikent@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=onestero@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