On Mon, Jan 29, 2018 at 2:44 PM, Ben Pfaff wrote:
> On Mon, Jan 29, 2018 at 02:35:35PM -0800, William Tu wrote:
>> On Mon, Jan 29, 2018 at 2:27 PM, Ben Pfaff wrote:
>> > On Mon, Jan 29, 2018 at 02:16:24PM -0800, William Tu wrote:
>> >> On Thu, Jan 25, 2018 at 3:39 PM,
On Mon, Jan 29, 2018 at 02:35:35PM -0800, William Tu wrote:
> On Mon, Jan 29, 2018 at 2:27 PM, Ben Pfaff wrote:
> > On Mon, Jan 29, 2018 at 02:16:24PM -0800, William Tu wrote:
> >> On Thu, Jan 25, 2018 at 3:39 PM, Ben Pfaff wrote:
> >> > ovs-vswitchd makes extensive
On Mon, Jan 29, 2018 at 2:27 PM, Ben Pfaff wrote:
> On Mon, Jan 29, 2018 at 02:16:24PM -0800, William Tu wrote:
>> On Thu, Jan 25, 2018 at 3:39 PM, Ben Pfaff wrote:
>> > ovs-vswitchd makes extensive use of RCU to defer freeing memory past the
>> > latest time that it
On Mon, Jan 29, 2018 at 02:16:24PM -0800, William Tu wrote:
> On Thu, Jan 25, 2018 at 3:39 PM, Ben Pfaff wrote:
> > ovs-vswitchd makes extensive use of RCU to defer freeing memory past the
> > latest time that it could be in use by a thread. Until now, ovs-vswitchd
> > has not
On Thu, Jan 25, 2018 at 3:39 PM, Ben Pfaff wrote:
> ovs-vswitchd makes extensive use of RCU to defer freeing memory past the
> latest time that it could be in use by a thread. Until now, ovs-vswitchd
> has not waited for RCU callbacks to fire before exiting. This meant that
> in
ovs-vswitchd makes extensive use of RCU to defer freeing memory past the
latest time that it could be in use by a thread. Until now, ovs-vswitchd
has not waited for RCU callbacks to fire before exiting. This meant that
in many cases, when ovs-vswitchd exits, many blocks of memory are stuck in