From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
linux-block@vger.kernel.org, io-uring <io-uring@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"Gohad, Tushar" <tushar.gohad@intel.com>,
Christoph Hellwig <hch@lst.de>,
Kanchan Joshi <joshi.k@samsung.com>,
Anuj Gupta <anuj20.g@samsung.com>,
Nitesh Shetty <nj.shetty@samsung.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LSF/MM/BPF TOPIC] dmabuf backed read/write
Date: Mon, 9 Feb 2026 09:24:17 -0400 [thread overview]
Message-ID: <20260209132417.GA3076640@nvidia.com> (raw)
In-Reply-To: <6246cc2b-0d6e-4062-ac24-74c7148dc47d@amd.com>
On Mon, Feb 09, 2026 at 02:09:24PM +0100, Christian König wrote:
> We have exercised and discussed this in absolutely detail and it is
> not going to fly anywhere.
Yes, I understand you concerns with struct page from past abuses.
> The struct page based approach in fundamentally incompatible with
> driver managed exporters.
The *general* struct page system is incompatible - but that is not
what I'm suggesting. I'm suggesting io_uring, and only io_uring could
use this with it fully implementing all the lifecycle rules that are
needed. Including move_notify and fences so that the driver managed
exporter has no issue.
Reworking the block stack to not rely on page is also a good path, but
probably alot harder. :\
Jason
next prev parent reply other threads:[~2026-02-09 13:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260204153051epcas5p1c2efd01ef32883680fed2541f9fca6c2@epcas5p1.samsung.com>
2026-02-03 14:29 ` [LSF/MM/BPF TOPIC] dmabuf backed read/write Pavel Begunkov
2026-02-03 18:07 ` Keith Busch
2026-02-04 6:07 ` Anuj Gupta/Anuj Gupta
2026-02-04 11:38 ` Pavel Begunkov
2026-02-04 15:26 ` Nitesh Shetty
2026-02-09 11:15 ` Pavel Begunkov
2026-02-05 3:12 ` Ming Lei
2026-02-05 18:13 ` Pavel Begunkov
2026-02-05 17:41 ` Jason Gunthorpe
2026-02-05 19:06 ` Pavel Begunkov
2026-02-05 23:56 ` Jason Gunthorpe
2026-02-06 15:08 ` Pavel Begunkov
2026-02-06 15:20 ` Jason Gunthorpe
2026-02-06 17:57 ` Pavel Begunkov
2026-02-06 18:37 ` Jason Gunthorpe
2026-02-09 10:59 ` Pavel Begunkov
2026-02-09 13:06 ` Jason Gunthorpe
2026-02-09 13:09 ` Christian König
2026-02-09 13:24 ` Jason Gunthorpe [this message]
2026-02-09 13:55 ` Christian König
2026-02-09 14:01 ` Jason Gunthorpe
2026-02-09 9:54 ` Kanchan Joshi
2026-02-09 10:13 ` Christian König
2026-02-09 12:54 ` Jason Gunthorpe
2026-02-09 10:04 ` Kanchan Joshi
2026-02-24 0:13 ` T.J. Mercier
2026-02-24 13:48 ` Pavel Begunkov
2026-02-26 23:38 ` Isaac Manjarres
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=20260209132417.GA3076640@nvidia.com \
--to=jgg@nvidia.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=christian.koenig@amd.com \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nj.shetty@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.