From: Christoph Hellwig <hch@infradead.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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: Tue, 18 Feb 2025 00:30:57 -0800 [thread overview]
Message-ID: <Z7RFQQoC5J7Dl6HC@infradead.org> (raw)
In-Reply-To: <hljsp2xn24z4hjebmrgluwcwvqokt2f6apcuuyd7z3xgfitagh@gk3wr4oh4xrt>
On Thu, Feb 13, 2025 at 02:26:37PM +0100, Daniel Gomez wrote:
> That's a good question. The stx_blksize field description indicates the value
> should be referring to the fs block size that avoids RMW.
One that is optimal, the RMW is an example. This what Posix says:
blksize_t st_blksize A file system-specific preferred I/O block size
for this object. In some file system types, this
may vary from file to file.
> So I think, if devices report high values in stx_blksize, it is either because
> smaller values than the reported one cause RMW or they are incorrectly reporting
> a value in the wrong statx field.
Or it is just more efficient. E.g. on NFS or XFS you'll get fairly
big values.
> The commit I refer in the commit message maps the minimum_io_size reported by
> the block layer with stx_blksize.
Yes, and that was my question again - minimum_io_size for block
devices is specified even more handwavy.
In other words I'm really sceptical this is going to be a net win.
To win me over you'll need to show a improvement over a wide variety
of devіces and workloads.
next prev parent reply other threads:[~2025-02-18 8: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
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 [this message]
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=Z7RFQQoC5J7Dl6HC@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