On Mon, Apr 22, 2013 at 9:26 PM, Ben Pfaff wrote:
> On Mon, Apr 22, 2013 at 05:10:21PM -0700, Gurucharan Shetty wrote:
> > On Mon, Apr 22, 2013 at 2:19 PM, Ben Pfaff wrote:
> >
> > > On Wed, Apr 17, 2013 at 03:11:12PM -0700, Gurucharan Shetty wrote:
> > > > Currently, when we upgrade openvswitch
On Mon, Apr 22, 2013 at 05:10:21PM -0700, Gurucharan Shetty wrote:
> On Mon, Apr 22, 2013 at 2:19 PM, Ben Pfaff wrote:
>
> > On Wed, Apr 17, 2013 at 03:11:12PM -0700, Gurucharan Shetty wrote:
> > > Currently, when we upgrade openvswitch packages, we do a restart
> > > of userspace daemons automat
On Mon, Apr 22, 2013 at 2:19 PM, Ben Pfaff wrote:
> On Wed, Apr 17, 2013 at 03:11:12PM -0700, Gurucharan Shetty wrote:
> > Currently, when we upgrade openvswitch packages, we do a restart
> > of userspace daemons automatically. This does not replace the
> > kernel module.
> >
> > But almost every
On Wed, Apr 17, 2013 at 03:11:12PM -0700, Gurucharan Shetty wrote:
> Currently, when we upgrade openvswitch packages, we do a restart
> of userspace daemons automatically. This does not replace the
> kernel module.
>
> But almost everytime, we want to use the new kernel module
> that comes with th
Currently, when we upgrade openvswitch packages, we do a restart
of userspace daemons automatically. This does not replace the
kernel module.
But almost everytime, we want to use the new kernel module
that comes with the new version. This means that we need to
manually do a "force-reload-kmod". Th
Currently, when we upgrade openvswitch packages, we do a restart
of userspace daemons automatically. This does not replace the
kernel module.
But almost everytime, we want to use the new kernel module
that comes with the new version. This means that we need to
manually do a "force-reload-kmod". Th
