From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-block@vger.kernel.org, hch@lst.de,
martin.petersen@oracle.com, axboe@kernel.dk,
Keith Busch <kbusch@kernel.org>
Subject: Re: [RFC PATCH] blk-integrity: support arbitrary buffer alignment
Date: Wed, 5 Nov 2025 15:15:04 +0100 [thread overview]
Message-ID: <20251105141504.GC22325@lst.de> (raw)
In-Reply-To: <20251104224045.3396384-1-kbusch@meta.com>
I have a hard time understanding how this actually works, mostly due to
"union pi_tuple". What does that union of two pointers buy us over just
passing a void pointer and deriving the type we need deeper down? Also
given that taking the address and the comparing it (at thbeginning of
blk_tuple_remap_end) how is this actually going to work?
next prev parent reply other threads:[~2025-11-05 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 22:40 [RFC PATCH] blk-integrity: support arbitrary buffer alignment Keith Busch
2025-11-05 14:15 ` Christoph Hellwig [this message]
2025-11-05 14:42 ` Keith Busch
2025-11-05 14:51 ` Keith Busch
2025-11-05 14:53 ` Christoph Hellwig
2025-11-05 16:28 ` Keith Busch
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=20251105141504.GC22325@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.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