All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/9] xfs: add a xfs_rmap_inode_owner helper
Date: Mon, 18 May 2026 15:28:09 +0200	[thread overview]
Message-ID: <20260518132809.GA8646@lst.de> (raw)
In-Reply-To: <agsSq64M1VbxMMqD@nidhogg.toxiclabs.cc>

On Mon, May 18, 2026 at 03:23:58PM +0200, Carlos Maiolino wrote:
> On Mon, May 18, 2026 at 03:16:39PM +0200, Christoph Hellwig wrote:
> > On Mon, May 18, 2026 at 01:14:31PM +0200, Carlos Maiolino wrote:
> > > On Fri, May 15, 2026 at 03:50:26PM +0200, Christoph Hellwig wrote:
> > > > Add a small wrapper for initializing the rmap owner to i_ino.
> > > > 
> > > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > 
> > > This and the previous one, provides very little gain IMHO, do you intend
> > > to get rid of xfs_rmap_ino_owner and xfs_rmap_inode_bmbt_owner? It seems
> > > to me they could simply be replaced by these new helpers instead of just
> > > wrapping them into these new ones.
> > > A little disclaimer: I didn't look into the next patches yet to see if
> > > it will all make sense later.
> > 
> > My direct aim was to reduce uses of i_ino so I looked for common
> > patterns.  I also generally prefer APIs that pass typesave objects
> > over those passing integers as handles wherever possible.
> 
> Agreed. both xfs_rmap_ino_owner and xfs_rmap_inode_bmbt_owner look good
> candidates to fully replace their 'old' versions giving all their
> callers have access to the xfs_inode (if I didn't miss any user).

We can't convert all, because repair needs to pass a different owner.

  reply	other threads:[~2026-05-18 13:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 13:50 remove struct xfs_inode.i_ino Christoph Hellwig
2026-05-15 13:50 ` [PATCH 1/9] xfs: add a XFS_INODE_TO_AGNO helper Christoph Hellwig
2026-05-18  9:21   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 2/9] xfs: add a XFS_INODE_TO_AGINO helper Christoph Hellwig
2026-05-18 11:04   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 3/9] xfs: add a XFS_INO_TO_FSB helper Christoph Hellwig
2026-05-18 11:06   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 4/9] xfs: add a xfs_rmap_inode_bmbt_owner Christoph Hellwig
2026-05-18 11:14   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 5/9] xfs: add a xfs_rmap_inode_owner helper Christoph Hellwig
2026-05-18 11:14   ` Carlos Maiolino
2026-05-18 13:16     ` Christoph Hellwig
2026-05-18 13:23       ` Carlos Maiolino
2026-05-18 13:28         ` Christoph Hellwig [this message]
2026-05-28  5:23       ` Darrick J. Wong
2026-05-28  8:28         ` Christoph Hellwig
2026-05-18 11:23   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 6/9] xfs: add a xchk_ip_set_corrupt helper Christoph Hellwig
2026-05-18 11:22   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 7/9] xfs: convert xchk_inode_xref_set_corrupt to xchk_ip_xref_set_corrupt Christoph Hellwig
2026-05-18 11:17   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 8/9] xfs: remove xfs_setup_existing_inode Christoph Hellwig
2026-05-18 11:18   ` Carlos Maiolino
2026-05-15 13:50 ` [PATCH 9/9] xfs: remove the i_ino field in struct xfs_inode Christoph Hellwig
2026-05-18 11:43   ` Carlos Maiolino
2026-05-28  5:24 ` remove struct xfs_inode.i_ino Darrick J. Wong
2026-05-29  4:33   ` Darrick J. Wong

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=20260518132809.GA8646@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=linux-xfs@vger.kernel.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 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.