All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] fs: make s_count atomic_t
Date: Tue, 7 Nov 2023 16:01:44 +0100	[thread overview]
Message-ID: <20231107-ersehen-zuerst-b184c0f91d85@brauner> (raw)
In-Reply-To: <20231106180831.GU1957730@ZenIV>

On Mon, Nov 06, 2023 at 06:08:31PM +0000, Al Viro wrote:
> On Fri, Nov 03, 2023 at 09:19:08AM +0100, Christoph Hellwig wrote:
> > Same feeling as Jan here - this looks fine to me, but I wonder if there's
> > much of a need.  Maybe run it past Al if he has any opinion?
> 
> [resurfaces from dcache stuff]
> 
> TBH, I'd rather see documentation of struct super_block life cycle
> rules written up, just to see what ends up being too ugly to document ;-/
> I have old notes on that stuff, but they are pretty much invalidated by
> the rework that happened this summer...

So I can write up an even more detailed document but
Documentation/filesystems/porting.rst upstream summarizes what has been
done in some detail.

> I don't hate making ->s_count atomic, but short of real evidence that
> sb_lock gets serious contention, I don't see much point either way.

Doesn't really matter enough imho.

> 
> PS: Re dcache - I've a growing branch with a bunch of massage in that area,
> plus the local attempt at documentation that will go there.  How are we
> going to manage the trees?  The coming cycle I'm probably back to normal
> amount of activity; the summer had been a fucking nightmare, but the things
> have settled down by now...  <looks> at least 5 topical branches, just
> going by what I've got at the moment.

One option is that I pull dcache branches from you and merge them into
vfs.all. I can also send them to Linus but I understand if you prefer to
do this yourself.

The other options is that you just do what you do in your tree and we'll
just deal with merge conflicts in next.

Fwiw, I haven't applied a lot of dcache stuff or taken patches of yours
you've Cced me on recently because I wasn't sure whether that was what
you wanted. I'm happy to pick them up ofc.

      reply	other threads:[~2023-11-07 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  9:35 [RFC PATCH] fs: make s_count atomic_t Christian Brauner
2023-11-02 13:48 ` Jan Kara
2023-11-02 16:05   ` Christian Brauner
2023-11-03  8:19 ` Christoph Hellwig
2023-11-06 18:08   ` Al Viro
2023-11-07 15:01     ` 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=20231107-ersehen-zuerst-b184c0f91d85@brauner \
    --to=brauner@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.