Re: [ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-08 Thread Jarno Rajahalme
> On Dec 8, 2015, at 11:41 AM, Ben Pfaff wrote: > > On Tue, Dec 08, 2015 at 11:39:23AM -0800, Jarno Rajahalme wrote: >> >>> On Dec 7, 2015, at 9:34 AM, Ben Pfaff wrote: >>> >>> On Fri, Dec 04, 2015 at 03:57:09PM -0800, Jarno Rajahalme wrote: Having a coverage counter tracking the value o

Re: [ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-08 Thread Ben Pfaff
On Tue, Dec 08, 2015 at 11:39:23AM -0800, Jarno Rajahalme wrote: > > > On Dec 7, 2015, at 9:34 AM, Ben Pfaff wrote: > > > > On Fri, Dec 04, 2015 at 03:57:09PM -0800, Jarno Rajahalme wrote: > >> Having a coverage counter tracking the value of the internal seq_next > >> should help in debugging. >

Re: [ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-08 Thread Justin Pettit
> On Dec 8, 2015, at 11:39 AM, Jarno Rajahalme wrote: > > >> On Dec 7, 2015, at 9:34 AM, Ben Pfaff wrote: >> >> On Fri, Dec 04, 2015 at 03:57:09PM -0800, Jarno Rajahalme wrote: >>> Having a coverage counter tracking the value of the internal seq_next >>> should help in debugging. >>> >>> Sug

Re: [ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-08 Thread Jarno Rajahalme
> On Dec 7, 2015, at 9:34 AM, Ben Pfaff wrote: > > On Fri, Dec 04, 2015 at 03:57:09PM -0800, Jarno Rajahalme wrote: >> Having a coverage counter tracking the value of the internal seq_next >> should help in debugging. >> >> Suggested-by: Justin Pettit >> Signed-off-by: Jarno Rajahalme > > Ac

Re: [ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-07 Thread Ben Pfaff
On Fri, Dec 04, 2015 at 03:57:09PM -0800, Jarno Rajahalme wrote: > Having a coverage counter tracking the value of the internal seq_next > should help in debugging. > > Suggested-by: Justin Pettit > Signed-off-by: Jarno Rajahalme Acked-by: Ben Pfaff

[ovs-dev] [PATCH] seq: Add a coverage counter for seq_change.

2015-12-04 Thread Jarno Rajahalme
Having a coverage counter tracking the value of the internal seq_next should help in debugging. Suggested-by: Justin Pettit Signed-off-by: Jarno Rajahalme --- lib/seq.c | 8 1 file changed, 8 insertions(+) diff --git a/lib/seq.c b/lib/seq.c index 271e617..9c3257c 100644 --- a/lib/seq.