All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] mkfs: enable new features by default
Date: Tue, 2 Dec 2025 22:31:22 -0800	[thread overview]
Message-ID: <aS_ZOpzcp04ovBwk@infradead.org> (raw)
In-Reply-To: <20251203005345.GD89492@frogsfrogsfrogs>

On Tue, Dec 02, 2025 at 04:53:45PM -0800, Darrick J. Wong wrote:
> On Mon, Dec 01, 2025 at 11:38:46PM -0800, Christoph Hellwig wrote:
> > On Mon, Dec 01, 2025 at 05:28:16PM -0800, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > > 
> > > Since the LTS is coming up, enable parent pointers and exchange-range by
> > > default for all users.  Also fix up an out of date comment.
> > 
> > Do you have any numbers that show the overhead or non-overhead of
> > enabling rmap?  It will increase the amount of metadata written quite
> > a bit.
> 
> I'm assuming you're interested in the overhead of *parent pointers* and
> not rmap since we turned on rmap by default back in 2023?

Yes, sorry.

> I see more or less the same timings for the nine subsequent runs for
> each parent= setting.  I think it's safe to say the overhead ranges
> between negligible and 10% on a cold new filesystem.

Should we document this cleary?  Because this means at least some
workloads are going to see a performance decrease.


  reply	other threads:[~2025-12-03  6:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02  1:27 [PATCHSET 2/2] xfsprogs: enable new stable features for 6.18 Darrick J. Wong
2025-12-02  1:28 ` [PATCH 1/2] mkfs: enable new features by default Darrick J. Wong
2025-12-02  7:38   ` Christoph Hellwig
2025-12-03  0:53     ` Darrick J. Wong
2025-12-03  6:31       ` Christoph Hellwig [this message]
2025-12-04 18:48         ` Darrick J. Wong
2025-12-02  1:28 ` [PATCH 2/2] mkfs: add 2025 LTS config file Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2025-12-09 16:16 [PATCHSET V2] xfsprogs: enable new stable features for 6.18 Darrick J. Wong
2025-12-09 16:16 ` [PATCH 1/2] mkfs: enable new features by default Darrick J. Wong
2025-12-09 16:22   ` Christoph Hellwig
2025-12-09 22:25   ` Dave Chinner
2025-12-10 23:49     ` Darrick J. Wong
2025-12-15 23:59       ` Dave Chinner
2025-12-16 23:07         ` 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=aS_ZOpzcp04ovBwk@infradead.org \
    --to=hch@infradead.org \
    --cc=aalbersh@kernel.org \
    --cc=djwong@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.