Hey Joe,
On Wed, Apr 9, 2014 at 6:16 PM, Joe Stringer wrote:
> It had occurred to me at the time, that this was a possible middle ground
> between making netdev change_seq completely global or retaining this
> per-netdev seq as well as having a global seq. When I looked at perf when
> many port
It had occurred to me at the time, that this was a possible middle ground
between making netdev change_seq completely global or retaining this
per-netdev seq as well as having a global seq. When I looked at perf when
many ports are configured, a majority of the cost seemed to be just in just
iterat
On Fri, Apr 04, 2014 at 03:00:36PM -0700, Alex Wang wrote:
> This commit can be seen as a partial revert of commit
> da4a619179d (netdev: Globally track port status changes)
> by adding the 'change_seq' to 'struct netdev'.
>
> Signed-off-by: Alex Wang
Acked-by: Ben Pfaff
___
This commit can be seen as a partial revert of commit
da4a619179d (netdev: Globally track port status changes)
by adding the 'change_seq' to 'struct netdev'.
Signed-off-by: Alex Wang
---
lib/netdev-bsd.c |5 +
lib/netdev-dpdk.c |1 +
lib/netdev-dummy.c|2 ++
lib/netd
