From: Christoph Hellwig <hch@lst.de>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: Kyle Bader <kbader@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Kyle Bader <kbader@ibm.com>, Anuj Gupta <anuj20.g@samsung.com>,
Kanchan Joshi <joshi.k@samsung.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tushar Gohad <tushar.gohad@intel.com>,
linux-block@vger.kernel.org, io-uring@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: only fail dma-buf bios that need block layer PI
Date: Thu, 29 Oct 2026 13:27:41 +0100 [thread overview]
Message-ID: <20261029122741.GB25162@lst.de> (raw)
In-Reply-To: <134aa376-7441-46e1-8d04-be327747b4a9@gmail.com>
On Thu, Oct 29, 2026 at 11:51:31AM +0000, Pavel Begunkov wrote:
> Thanks, looks good from a quick glance, I'll take another look in
> a bit. It might be nice to somehow support kernel generated PI
> as well later, looks like there will be a good bunch of cases that
> might want to have CPU access.
I don't think the kernel auto-PI makes sense for P2P. The data lives
on a remote device, so generating PI for it would have to transfer
the data to the host. Instead we probably should just force PRACT
for that case. It would make sense to support PI generation for
dmabufs using local memory, though.
next prev parent reply other threads:[~2026-10-29 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:14 [PATCH] block: only fail dma-buf bios that need block layer PI Kyle Bader
2026-10-29 11:33 ` Anuj gupta
2026-10-29 11:51 ` Pavel Begunkov
2026-10-29 12:27 ` Christoph Hellwig [this message]
2026-10-29 12:20 ` 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=20261029122741.GB25162@lst.de \
--to=hch@lst.de \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbader@ibm.com \
--cc=kbader@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=tushar.gohad@intel.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