From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] vfs dio
Date: Tue, 28 Jan 2025 22:34:32 -0800 [thread overview]
Message-ID: <Z5nL-NOQrAlaWNjy@infradead.org> (raw)
In-Reply-To: <CAHk-=wj+uVo3sJU3TKup0QfftWaEXcaiH4aBqnuM09eUDdo=og@mail.gmail.com>
[Sorry for the delay, I've been distrracted by a fun mix of personal
business and urgend customer work]
On Mon, Jan 20, 2025 at 11:24:56AM -0800, Linus Torvalds wrote:
> On Sat, 18 Jan 2025 at 05:09, Christian Brauner <brauner@kernel.org> wrote:
> >
> > Add a separate dio read align field to statx, as many out of place write
> > file systems can easily do reads aligned to the device sector size, but
> > require bigger alignment for writes.
>
> I've pulled this, but it needs some fixing.
>
> You added the 'dio_read_offset_align' field to 'struct kstat', and
> that structure is *critical*, because it's used even for the real
> 'stat()' calls that people actually use (as opposed to the statx side
> that is seldom a real issue).
>
> And that field was added in a way that causes the struct to grow due
> to alignment issues. For no good reason, because there were existing
> holes in there.
Indeed, sorry. I put all attention on the user visible struct statx
and missed optimizing the in-kernel kstat.
> I despise the whole statx thing exactly because it has (approximately)
> five specialized users, while slowing down regular stat/fstat that is
> used widely absolutely *evertwhere*.
Yeah. I still hate the statx design as it overload the critical
stat information with all the misc based path information that is
useful in some cases but not actually needed for most. Not much
we can do about that now, though.
next prev parent reply other threads:[~2025-01-29 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 13:09 Christian Brauner
2025-01-20 19:24 ` Linus Torvalds
2025-01-20 19:38 ` Christian Brauner
2025-01-20 19:50 ` Linus Torvalds
2025-01-22 13:50 ` Christian Brauner
2025-01-20 19:39 ` Linus Torvalds
2025-01-29 6:34 ` Christoph Hellwig [this message]
2025-01-20 19:51 ` pr-tracker-bot
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=Z5nL-NOQrAlaWNjy@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®