Re: [ovs-dev] [PATCH] RFC datapath-windows: Create com device only when extension is enabled

2018-04-05 Thread Shashank Ram
From: aserd...@ovn.org <aserd...@ovn.org> Sent: Thursday, April 5, 2018 2:32 AM To: Shashank Ram; d...@openvswitch.org Subject: RE: [ovs-dev] [PATCH] RFC datapath-windows: Create com device only when extension is enabled > -Mesaj

Re: [ovs-dev] [PATCH] RFC datapath-windows: Create com device only when extension is enabled

2018-04-05 Thread aserdean
ay, April 3, 2018 8:08 AM > To: d...@openvswitch.org > Cc: Alin Gabriel Serdean > Subject: [ovs-dev] [PATCH] RFC datapath-windows: Create com device only > whenextension is enabled > > Until now the communication device between the kernel and userspace > is created when the

Re: [ovs-dev] [PATCH] RFC datapath-windows: Create com device only when extension is enabled

2018-04-04 Thread Shashank Ram
RFC datapath-windows: Create com device only when extension is enabled Until now the communication device between the kernel and userspace is created when the network driver is installed. Since we only do processing if the Hyper-V vSwitch extension is enabled by the user, it makes more s

[ovs-dev] [PATCH] RFC datapath-windows: Create com device only when extension is enabled

2018-04-03 Thread Alin Gabriel Serdean
Until now the communication device between the kernel and userspace is created when the network driver is installed. Since we only do processing if the Hyper-V vSwitch extension is enabled by the user, it makes more sense to move the device creation only when that is true. Signed-off-by: Alin