public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: da.gomez@kernel.org
Cc: linux-xfs@vger.kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
	Daniel Gomez <da.gomez@samsung.com>,
	Pankaj Raghav <p.raghav@samsung.com>,
	gost.dev@samsung.com
Subject: Re: [PATCH] mkfs: use stx_blksize for dev block size by default
Date: Thu, 6 Feb 2025 20:30:22 -0800	[thread overview]
Message-ID: <Z6WMXlJrgIIbgNV7@infradead.org> (raw)
In-Reply-To: <20250206-min-io-default-blocksize-v1-1-2312e0bb8809@samsung.com>

On Thu, Feb 06, 2025 at 07:00:55PM +0000, da.gomez@kernel.org wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
> 
> In patch [1] ("bdev: use bdev_io_min() for statx block size"), block
> devices will now report their preferred minimum I/O size for optimal
> performance in the stx_blksize field of the statx data structure. This
> change updates the current default 4 KiB block size for all devices
> reporting a minimum I/O larger than 4 KiB, opting instead to query for
> its advertised minimum I/O value in the statx data struct.

UUuh, no.  Larger block sizes have their use cases, but this will
regress performance for a lot (most?) common setups.  A lot of
device report fairly high values there, but say increasing the
directory and bmap btree block size unconditionally using the current
algorithms will dramatically increase write amplification.  Similarly
for small buffered writes.


  parent reply	other threads:[~2025-02-07  4:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 19:00 [PATCH] mkfs: use stx_blksize for dev block size by default da.gomez
2025-02-06 22:27 ` Darrick J. Wong
2025-02-06 22:50   ` Luis Chamberlain
2025-02-06 23:07     ` Darrick J. Wong
2025-02-07  9:12     ` Daniel Gomez
2025-02-07 19:16       ` Luis Chamberlain
2025-02-07  9:39   ` Daniel Gomez
2025-02-07 19:26   ` Luis Chamberlain
2025-02-07 19:31     ` Darrick J. Wong
2025-02-07 19:44       ` Luis Chamberlain
2025-02-07  4:30 ` Christoph Hellwig [this message]
2025-02-07 10:04   ` Daniel Gomez
2025-02-13  4:10     ` Christoph Hellwig
2025-02-13 13:26       ` Daniel Gomez
2025-02-18  8:30         ` Christoph Hellwig
2025-05-09 14:27           ` Luis Chamberlain
2025-05-13  5:33             ` Christoph Hellwig

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=Z6WMXlJrgIIbgNV7@infradead.org \
    --to=hch@infradead.org \
    --cc=da.gomez@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=gost.dev@samsung.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.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