linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Chuck Lever <cel@kernel.org>, oliver.sang@intel.com
Cc: Christian Brauner <brauner@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	oe-lkp@lists.linux.dev, ying.huang@intel.com,
	feng.tang@intel.com, fengwei.yin@intel.com,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH RFC] libfs: Remove parent dentry locking in offset_iterate_dir()
Date: Fri, 28 Jul 2023 10:06:49 +0200	[thread overview]
Message-ID: <20230728-sorglos-krempel-7f7b18c4c247@brauner> (raw)
In-Reply-To: <169030957098.157536.9938425508695693348.stgit@manet.1015granger.net>

On Tue, 25 Jul 2023 14:31:04 -0400, Chuck Lever wrote:
> Since offset_iterate_dir() does not walk the parent's d_subdir list
> nor does it manipulate the parent's d_child, there doesn't seem to
> be a reason to hold the parent's d_lock. The offset_ctx's xarray can
> be sufficiently protected with just the RCU read lock.
> 
> Flame graph data captured during the git regression run shows a
> 20% reduction in CPU cycles consumed in offset_find_next().
> 
> [...]

I've picked this up. It would be very nice if we could get a perf test
from lkp for this fix.

---

Applied to the vfs.tmpfs branch of the vfs/vfs.git tree.
Patches in the vfs.tmpfs branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.tmpfs

[1/1] libfs: Remove parent dentry locking in offset_iterate_dir()
      https://git.kernel.org/vfs/vfs/c/01c45fd0472c


      reply	other threads:[~2023-07-28  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 18:31 Chuck Lever
2023-07-28  8:06 ` Christian Brauner [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=20230728-sorglos-krempel-7f7b18c4c247@brauner \
    --to=brauner@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=ying.huang@intel.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