[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yd2MeMT6LXWxJIDd@casper.infradead.org>
Date: Tue, 11 Jan 2022 13:56:08 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Thomas Zimmermann <tzimmermann@...e.de>
Cc: linux-kernel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-rdma@...r.kernel.org, John Hubbard <jhubbard@...dia.com>,
dri-devel@...ts.freedesktop.org, Ming Lei <ming.lei@...hat.com>,
linux-block@...r.kernel.org, linux-mm@...ck.org,
Jason Gunthorpe <jgg@...dia.com>, netdev@...r.kernel.org,
Joao Martins <joao.m.martins@...cle.com>,
Logan Gunthorpe <logang@...tatee.com>,
Christoph Hellwig <hch@....de>
Subject: Re: Phyr Starter
On Tue, Jan 11, 2022 at 12:40:10PM +0100, Thomas Zimmermann wrote:
> Hi
>
> Am 10.01.22 um 20:34 schrieb Matthew Wilcox:
> > TLDR: I want to introduce a new data type:
> >
> > struct phyr {
> > phys_addr_t addr;
> > size_t len;
> > };
>
> Did you look at struct dma_buf_map? [1]
Thanks. I wasn't aware of that. It doesn't seem to actually solve the
problem, in that it doesn't carry any length information. Did you mean
to point me at a different structure?
Powered by blists - more mailing lists