From: Bart Van Assche <bvanassche@acm.org>
To: Jason Gunthorpe <jgg@nvidia.com>, Matthew Wilcox <willy@infradead.org>
Cc: lsf-pc@lists.linuxfoundation.org, linux-mm@kvack.org,
iommu@lists.linux.dev, linux-rdma@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Joao Martins <joao.m.martins@oracle.com>,
John Hubbard <jhubbard@nvidia.com>,
Logan Gunthorpe <logang@deltatee.com>,
Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, nvdimm@lists.linux.dev,
Shakeel Butt <shakeelb@google.com>
Subject: Re: [LSF/MM/BPF proposal]: Physr discussion
Date: Mon, 23 Jan 2023 11:47:23 -0800 [thread overview]
Message-ID: <771236a2-b746-368d-f15f-23585f760ebd@acm.org> (raw)
In-Reply-To: <Y86PRiNCUIKbfUZz@nvidia.com>
On 1/23/23 05:44, Jason Gunthorpe wrote:
> I've gone from quite a different starting point - I've been working
> DMA API upwards, so what does the dma_map_XX look like, what APIs do
> we need to support the dma_map_ops implementations to iterate/etc, how
> do we form and return the dma mapped list, how does P2P, with all the
> checks, actually work, etc. These help inform what we want from the
> "phyr" as an API.
I'm interested in this topic. I'm wondering whether eliminating
scatterlists could help to make the block layer faster.
Thanks,
Bart.
next prev parent reply other threads:[~2023-01-23 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 15:03 [LSF/MM/BPF proposal]: Physr discussion Jason Gunthorpe
2023-01-23 4:36 ` Matthew Wilcox
2023-01-23 13:44 ` Jason Gunthorpe
2023-01-23 19:47 ` Bart Van Assche [this message]
2023-01-24 6:15 ` Chaitanya Kulkarni
2023-01-26 9:39 ` Mike Rapoport
2023-01-23 19:36 ` [Lsf-pc] " Dan Williams
2023-01-23 20:11 ` Matthew Wilcox
2023-01-23 20:50 ` Dan Williams
2023-01-23 22:46 ` Matthew Wilcox
2023-01-26 19:38 ` Jason Gunthorpe
2023-01-26 1:45 ` Zhu Yanjun
2023-02-28 20:59 ` T.J. Mercier
2023-04-17 19:59 ` Jason Gunthorpe
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=771236a2-b746-368d-f15f-23585f760ebd@acm.org \
--to=bvanassche@acm.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=ming.lei@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=shakeelb@google.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).