Re: [RFC] EAL: legacy memory fixed address translations

2022-07-28 Thread Dmitry Kozlyuk
2022-07-28 11:41 (UTC-0400), Don Wallwork: > On 7/28/2022 10:46 AM, Don Wallwork wrote: > Let me try to give a trivial example of how it would work > to make sure we're on the same page and then we can get > back to details.. > >>> Thanks you, Don. > >>> Now it's perfectly clear wh

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-28 Thread Don Wallwork
On 7/28/2022 10:46 AM, Don Wallwork wrote: Let me try to give a trivial example of how it would work to make sure we're on the same page and then we can get back to details.. Thanks you, Don. Now it's perfectly clear what EAL should do and we can discuss API. I think this RFC is an excellent pr

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-28 Thread Don Wallwork
On 7/28/2022 7:29 AM, Morten Brørup wrote: Let me try to give a trivial example of how it would work to make sure we're on the same page and then we can get back to details.. Thanks you, Don. Now it's perfectly clear what EAL should do and we can discuss API. I think this RFC is an excellent pr

RE: [RFC] EAL: legacy memory fixed address translations

2022-07-28 Thread Morten Brørup
> From: Dmitry Kozlyuk [mailto:dmitry.kozl...@gmail.com] > Sent: Thursday, 28 July 2022 09.26 > > 2022-07-27 17:43 (UTC-0400), Don Wallwork: > > On 7/27/2022 4:36 PM, Dmitry Kozlyuk wrote: > > > I now understand more about_why_ you want this feature > > > but became less confident_what_ do you'r

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-28 Thread Dmitry Kozlyuk
2022-07-27 17:43 (UTC-0400), Don Wallwork: > On 7/27/2022 4:36 PM, Dmitry Kozlyuk wrote: > > I now understand more about_why_ you want this feature > > but became less confident_what_ do you're proposing specifically. > > Let me try to give a trivial example of how it would work > to make sure

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-27 Thread Don Wallwork
On 7/27/2022 4:36 PM, Dmitry Kozlyuk wrote: I now understand more about_why_ you want this feature but became less confident_what_ do you're proposing specifically. Let me try to give a trivial example of how it would work to make sure we're on the same page and then we can get back to detail

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-27 Thread Dmitry Kozlyuk
I now understand more about _why_ you want this feature but became less confident _what_ do you're proposing specifically. >> 2022-07-26 14:33 (UTC-0400), Don Wallwork: >>> This proposal describes a method for translating any huge page >>> address from virtual to physical or vice versa using sim

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-27 Thread Don Wallwork
On 7/27/2022 3:12 PM, Stephen Hemminger wrote: On Wed, 27 Jul 2022 13:20:22 -0400 Don Wallwork wrote: When drivers need to process a large number of memory blocks, these are typically packets in the form of mbufs, which already have IOVA attached, so there is no translation. Does translation o

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-27 Thread Stephen Hemminger
On Wed, 27 Jul 2022 13:20:22 -0400 Don Wallwork wrote: > > > > When drivers need to process a large number of memory blocks, > > these are typically packets in the form of mbufs, > > which already have IOVA attached, so there is no translation. > > Does translation of mbuf VA to PA with the propo

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-27 Thread Don Wallwork
On 7/26/2022 3:59 PM, Dmitry Kozlyuk wrote: Hi Don, 2022-07-26 14:33 (UTC-0400), Don Wallwork: This proposal describes a method for translating any huge page address from virtual to physical or vice versa using simple addition or subtraction of a single fixed value. This allows devices to effic

Re: [RFC] EAL: legacy memory fixed address translations

2022-07-26 Thread Dmitry Kozlyuk
Hi Don, 2022-07-26 14:33 (UTC-0400), Don Wallwork: > This proposal describes a method for translating any huge page > address from virtual to physical or vice versa using simple > addition or subtraction of a single fixed value. This allows > devices to efficiently access arbitrary huge page memor