Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Carlos Maiolino <cem@kernel.org>,
	Lukas Herbolt <lukas@herbolt.com>,
	hch@infradead.org, aalbersh@redhat.com,
	linux-xfs@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>,
	ailiopoulos@suse.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] mkfs.xfs fix sunit size on 512e and 4kN disks.
Date: Tue, 23 Jun 2026 07:41:10 -0700	[thread overview]
Message-ID: <ajqbBiJqOije9z4N@infradead.org> (raw)
In-Reply-To: <yvjbtwfl4wfctmowoxpkzqhlqt42r2sns6p3t4j5ge3abv2ydr@degtb3bjzp4c>

On Mon, Jun 22, 2026 at 12:05:25PM +0200, Jan Kara wrote:
> > by accident. Properly aligning it to 64k to match its min_io_size is the
> > right thing to do to avoid lots of RMW cycles for once. But I'm pretty
> > sure you already know that :)
> 
> Yes, I agree the XFS logging with the old defaults performed well on that
> machine only due to the battery backed cache.

Which to me suggests it is reporting the wrong min_io_size.  But good
luck getting RAID controller firmware fixed.  Although maybe we should
quirk it in the driver?

> > Well, I don't think 'fsync heavy' applications are the default, or if
> > they are, specially on high-end systems, then I'd argue the application
> > ought to know what it's doing. I do agree that's no universal win
> > anywhere and yet seem to fix the sunit to the hardware reported size is
> > the right thing to do here.
> 
> Fair.

I think the real question is if the value/defaults have any benefits
for this setup.  And I somehow doubt it.


      reply	other threads:[~2026-06-23 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 11:44 [PATCH 0/1] mkfs.xfs fix sunit size on 512e and 4kN disks Lukas Herbolt
2026-02-19 11:44 ` [PATCH 1/1] " Lukas Herbolt
2026-02-19 13:32   ` Christoph Hellwig
2026-03-04 19:49   ` Darrick J. Wong
2026-06-15 13:17   ` Jan Kara
2026-06-22  9:07     ` Carlos Maiolino
2026-06-22 10:05       ` Jan Kara
2026-06-23 14:41         ` Christoph Hellwig [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=ajqbBiJqOije9z4N@infradead.org \
    --to=hch@infradead.org \
    --cc=aalbersh@redhat.com \
    --cc=ailiopoulos@suse.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lukas@herbolt.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