Re: [ovs-dev] [PATCH] ovs-ctl: Don't remember vport-* kernel modules

2017-11-27 Thread Eric Garver
On Fri, Nov 10, 2017 at 02:45:05PM -0800, Gurucharan Shetty wrote: > From OVS 2.8, ovs-vswitchd, when it starts, will > load the kernel modules for tunnels. It has logic > inside it to choose either upstream kernel module > or vport-* kernel module. > > So, when we run 'force-reload-kmod' to

Re: [ovs-dev] [PATCH] ovs-ctl: Don't remember vport-* kernel modules

2017-11-13 Thread Guru Shetty
On 13 November 2017 at 06:43, William Tu wrote: > On Fri, Nov 10, 2017 at 2:45 PM, Gurucharan Shetty wrote: > > From OVS 2.8, ovs-vswitchd, when it starts, will > > load the kernel modules for tunnels. It has logic > > inside it to choose either upstream kernel

Re: [ovs-dev] [PATCH] ovs-ctl: Don't remember vport-* kernel modules

2017-11-13 Thread William Tu
On Fri, Nov 10, 2017 at 2:45 PM, Gurucharan Shetty wrote: > From OVS 2.8, ovs-vswitchd, when it starts, will > load the kernel modules for tunnels. It has logic > inside it to choose either upstream kernel module > or vport-* kernel module. > > So, when we run 'force-reload-kmod' to

[ovs-dev] [PATCH] ovs-ctl: Don't remember vport-* kernel modules

2017-11-10 Thread Gurucharan Shetty
>From OVS 2.8, ovs-vswitchd, when it starts, will load the kernel modules for tunnels. It has logic inside it to choose either upstream kernel module or vport-* kernel module. So, when we run 'force-reload-kmod' to upgrade to OVS 2.8 from a previous version, we do not need to remember the