[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99b6e349-7241-807a-1b00-9b783a9555bc@nvidia.com>
Date: Thu, 21 Jul 2022 11:55:17 +0300
From: Yishai Hadas <yishaih@...dia.com>
To: "Tian, Kevin" <kevin.tian@...el.com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"jgg@...dia.com" <jgg@...dia.com>
CC: "saeedm@...dia.com" <saeedm@...dia.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"kuba@...nel.org" <kuba@...nel.org>,
"Martins, Joao" <joao.m.martins@...cle.com>,
"leonro@...dia.com" <leonro@...dia.com>,
"maorg@...dia.com" <maorg@...dia.com>,
"cohuck@...hat.com" <cohuck@...hat.com>
Subject: Re: [PATCH V2 vfio 00/11] Add device DMA logging support for mlx5
driver
On 21/07/2022 11:26, Tian, Kevin wrote:
>> From: Yishai Hadas <yishaih@...dia.com>
>> Sent: Thursday, July 14, 2022 4:13 PM
>>
>> It abstracts how an IOVA range is represented in a bitmap that is
>> granulated by a given page_size. So it translates all the lifting of
>> dealing with user pointers into its corresponding kernel addresses
>> backing said user memory into doing finally the bitmap ops to change
>> various bits.
>>
> Don't quite understand the last sentence...
It would come to say that this new functionality abstracts the
complexity of user/kernel bitmap pointer usage and finally enables an
easy way to set some bits.
I may rephrase as part of V3 to let it be clearer.
Yishai
Powered by blists - more mailing lists