On 3/22/23 13:54, Aaron Conole wrote:
> Ilya Maximets writes:
>
>> On 3/16/23 13:00, Aaron Conole wrote:
>>> Open vSwitch generally tries to let the underlying operating system
>>> managed the low level details of hardware, for example DMA mapping,
>>> bus arbitration, etc. However, when using
Ilya Maximets writes:
> On 3/16/23 13:00, Aaron Conole wrote:
>> Open vSwitch generally tries to let the underlying operating system
>> managed the low level details of hardware, for example DMA mapping,
>> bus arbitration, etc. However, when using DPDK, the underlying
>> operating system
On 3/16/23 13:00, Aaron Conole wrote:
> Open vSwitch generally tries to let the underlying operating system
> managed the low level details of hardware, for example DMA mapping,
> bus arbitration, etc. However, when using DPDK, the underlying
> operating system yields control of many of these
> From: Aaron Conole
> Date: Thursday, 16 March 2023 at 13:00
> To: d...@openvswitch.org
> Cc: Robin Jarry , Gaetan Rivet , Ilya
> Maximets , Eli Britstein , Maxime
> Coquelin , Jason Gunthorpe ,
> Majd Dibbiny , David Marchand march...@redhat.com>, Simon Horman , Flavio
> Leitner
>
On Thu, Mar 16, 2023 at 08:00:39AM -0400, Aaron Conole wrote:
> Open vSwitch generally tries to let the underlying operating system
> managed the low level details of hardware, for example DMA mapping,
> bus arbitration, etc. However, when using DPDK, the underlying
> operating system yields
Open vSwitch generally tries to let the underlying operating system
managed the low level details of hardware, for example DMA mapping,
bus arbitration, etc. However, when using DPDK, the underlying
operating system yields control of many of these details to userspace
for management.
In the case
