[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <771236a2-b746-368d-f15f-23585f760ebd@acm.org>
Date: Mon, 23 Jan 2023 11:47:23 -0800
From: Bart Van Assche <bvanassche@....org>
To: Jason Gunthorpe <jgg@...dia.com>,
Matthew Wilcox <willy@...radead.org>
Cc: lsf-pc@...ts.linuxfoundation.org, linux-mm@...ck.org,
iommu@...ts.linux.dev, linux-rdma@...r.kernel.org,
Christoph Hellwig <hch@....de>,
Joao Martins <joao.m.martins@...cle.com>,
John Hubbard <jhubbard@...dia.com>,
Logan Gunthorpe <logang@...tatee.com>,
Ming Lei <ming.lei@...hat.com>, linux-block@...r.kernel.org,
netdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
nvdimm@...ts.linux.dev, Shakeel Butt <shakeelb@...gle.com>
Subject: Re: [LSF/MM/BPF proposal]: Physr discussion
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.
Powered by blists - more mailing lists