On Tue, Apr 16, 2013 at 07:32:43PM -0700, Gurucharan Shetty wrote:
> On Tue, Apr 16, 2013 at 2:54 PM, Ben Pfaff wrote:
>
> > On Thu, Apr 11, 2013 at 04:40:13PM -0700, Ben Pfaff wrote:
> > > On Wed, Apr 10, 2013 at 03:41:23PM -0700, Gurucharan Shetty wrote:
> > > > Currently, when we upgrade openv
On Tue, Apr 16, 2013 at 2:54 PM, Ben Pfaff wrote:
> On Thu, Apr 11, 2013 at 04:40:13PM -0700, Ben Pfaff wrote:
> > On Wed, Apr 10, 2013 at 03:41:23PM -0700, Gurucharan Shetty wrote:
> > > Currently, when we upgrade openvswitch packages, we do restart
> > > of userspace daemons. This does not repl
On Thu, Apr 11, 2013 at 04:40:13PM -0700, Ben Pfaff wrote:
> On Wed, Apr 10, 2013 at 03:41:23PM -0700, Gurucharan Shetty wrote:
> > Currently, when we upgrade openvswitch packages, we do restart
> > of userspace daemons. This does not replace the kernel module.
> >
> > But almost everytime, we wan
On Wed, Apr 10, 2013 at 03:41:23PM -0700, Gurucharan Shetty wrote:
> Currently, when we upgrade openvswitch packages, we do restart
> of userspace daemons. This does not replace the kernel module.
>
> But almost everytime, we want to also use the new kernel module
> that comes with the new version
Currently, when we upgrade openvswitch packages, we do restart
of userspace daemons. This does not replace the kernel module.
But almost everytime, we want to also use the new kernel module
that comes with the new version. This means that we need to
manually do a "force-reload-kmod". This step, al
