On 01/07/2021 22:34, Flavio Leitner wrote:
>
> Hi Mark,
>
> One more thing, this seems a relevant change to mention in the
> NEWS file.
>
Done
> Thanks,
> fbl
>
> On Wed, Jun 30, 2021 at 05:56:11AM -0400, Mark Gray wrote:
>> The Open vSwitch kernel module uses the upcall mechanism to send
>>
On 01/07/2021 21:51, Flavio Leitner wrote:
>
> Hi Mark,
>
> I've not tested this yet.
> See some comments below.
>
> On Wed, Jun 30, 2021 at 05:56:11AM -0400, Mark Gray wrote:
>> The Open vSwitch kernel module uses the upcall mechanism to send
>> packets from kernel space to user space when it
Hi Mark,
One more thing, this seems a relevant change to mention in the
NEWS file.
Thanks,
fbl
On Wed, Jun 30, 2021 at 05:56:11AM -0400, Mark Gray wrote:
> The Open vSwitch kernel module uses the upcall mechanism to send
> packets from kernel space to user space when it misses in the kernel
>
Hi Mark,
I've not tested this yet.
See some comments below.
On Wed, Jun 30, 2021 at 05:56:11AM -0400, Mark Gray wrote:
> The Open vSwitch kernel module uses the upcall mechanism to send
> packets from kernel space to user space when it misses in the kernel
> space flow table. The upcall sends
The Open vSwitch kernel module uses the upcall mechanism to send
packets from kernel space to user space when it misses in the kernel
space flow table. The upcall sends packets via a Netlink socket.
Currently, a Netlink socket is created for every vport. In this way,
there is a 1:1 mapping between
