[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9486843d-bbef-f7e0-354c-2522ea3f896f@suse.de>
Date: Tue, 11 Jan 2022 15:10:00 +0100
From: Thomas Zimmermann <tzimmermann@...e.de>
To: Matthew Wilcox <willy@...radead.org>
Cc: nvdimm@...ts.linux.dev, linux-rdma@...r.kernel.org,
John Hubbard <jhubbard@...dia.com>,
linux-kernel@...r.kernel.org, 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
Hi
Am 11.01.22 um 14:56 schrieb Matthew Wilcox:
> 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?
>
It's the structure I meant. It refers to a buffer, so the length could
be added. For something more sophisticated, dma_buf_map could be changed
to distinguish between the buffer and an iterator pointing into the buffer.
But if it's really different, then so be it.
Best regards
Thomas
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
Download attachment "OpenPGP_signature" of type "application/pgp-signature" (841 bytes)
Powered by blists - more mailing lists