linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Chuck Lever <cel@kernel.org>, Jeff Layton <jlayton@kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] shmemfs stable directory offsets
Date: Wed, 21 Jun 2023 13:12:46 +0000	[thread overview]
Message-ID: <B3ADB232-DA75-45E9-9F7B-CB7BF524F713@oracle.com> (raw)
In-Reply-To: <168605676256.32244.6158641147817585524.stgit@manet.1015granger.net>



> On Jun 6, 2023, at 9:10 AM, Chuck Lever <cel@kernel.org> wrote:
> 
> The following series is for continued discussion of the need for
> and implementation of stable directory offsets for shmemfs/tmpfs.
> 
> As discussed in Vancouver, I've re-implemented this change in libfs
> so that other "simple" filesystems can use it. There were a few
> other suggestions made during that event that I haven't tried yet.
> 
> Changes since v2:
> - Move bulk of stable offset support into fs/libfs.c
> - Replace xa_find_after with xas_find_next for efficiency
> 
> Changes since v1:
> - Break the single patch up into a series
> 
> Changes since RFC:
> - Destroy xarray in shmem_destroy_inode() instead of free_in_core_inode()
> - A few cosmetic updates
> 
> ---
> 
> Chuck Lever (3):
>      libfs: Add directory operations for stable offsets
>      shmem: Refactor shmem_symlink()
>      shmem: stable directory offsets
> 
> 
> fs/dcache.c            |   1 +
> fs/libfs.c             | 185 +++++++++++++++++++++++++++++++++++++++++
> include/linux/dcache.h |   1 +
> include/linux/fs.h     |   9 ++
> mm/shmem.c             |  58 +++++++++----
> 5 files changed, 240 insertions(+), 14 deletions(-)

The good news is that so far I have received no complaints from bots
on this series.

The bad news is I have received no human comments. Ping?


--
Chuck Lever




       reply	other threads:[~2023-06-21 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168605676256.32244.6158641147817585524.stgit@manet.1015granger.net>
2023-06-21 13:12 ` Chuck Lever III [this message]
2023-06-21 14:25   ` Christian Brauner
     [not found] ` <168605705924.32244.13384849924097654559.stgit@manet.1015granger.net>
2023-06-23 22:21   ` [PATCH v3 1/3] libfs: Add directory operations for stable offsets Bernd Schubert
2023-06-26 13:36     ` Bernd Schubert
2023-06-26 14:50       ` Chuck Lever III
2023-06-26 15:01         ` Bernd Schubert
2023-06-26 15:22       ` Bernd Schubert
     [not found] ` <168605707262.32244.4794425063054676856.stgit@manet.1015granger.net>
2023-06-26 13:18   ` [PATCH v3 3/3] shmem: stable directory offsets Bernd Schubert
2023-06-26 15:16     ` Chuck Lever III

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=B3ADB232-DA75-45E9-9F7B-CB7BF524F713@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=cel@kernel.org \
    --cc=hughd@google.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@zeniv.linux.org.uk \
    /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