[RFC] EAL: legacy memory fixed address translations

[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 proposal!

Thanks Morten and Dmitry. Great to hear that.  When we have a
patch ready, will post on the list.

>
> Long term, I also hope that it can lead to the removal of the mbuf->buf_iova field, making it available for other purposes - e.g. moving the mbuf->next field up here, so rte_pktmbuf_free(), rte_pktmbuf_prefree_seg() and other functions don't have to touch the mbuf's second cache line anymore.
>

Yes, it does seem possible that this could be done once the fixed
translation logic is in place.