[ovs-dev] [ovs-dev, v9, 02/10] Present tracked changes in increasing change number order

Ryan Moats rmoats at us.ibm.com
Wed Mar 23 13:26:43 UTC 2016


Ben Pfaff <blp at ovn.org> wrote on 03/22/2016 04:37:50 PM:

> From: Ben Pfaff <blp at ovn.org>
> To: Ryan Moats/Omaha/IBM at IBMUS, Shad Ansari <shad.ansar at hpe.com>
> Cc: dev at openvswitch.org
> Date: 03/22/2016 04:38 PM
> Subject: Re: [ovs-dev, v9, 02/10] Present tracked changes in
> increasing change number order
>
> On Fri, Mar 11, 2016 at 03:06:17PM -0600, Ryan Moats wrote:
> > From: RYAN D. MOATS <rmoats at us.ibm.com>
> >
> > Currently changes are added to the front of the track list, so
> > they are looped through in LIFO order. Incremental processing
> > is more efficient with a FIFO presentation, so
> > (1) add new changes to the back of the track list, and
> > (2) move updated changes to the back of the track list
> >
> > Signed-off-by: RYAN D. MOATS <rmoats at us.ibm.com>
>
> I applied this because it makes a lot of sense to me: it causes changes
> to be presented in their natural order, that is, in the order in which
> they were received.  I'm copying Shad, the original author of the column
> tracking code, on this message in case he wants to advocate that the
> previous order was superior.
>
> Thanks,
>
> Ben.
>

Thanks Ben, and FYI, I've got lots of reasons (read scars) for why I think
the previous order is *not* superior - I'll be happy to share them (if need
be)...

Ryan (regXboi)



More information about the dev mailing list