[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170222010816.9676-1-mahesh@bandewar.net>
Date: Tue, 21 Feb 2017 17:08:16 -0800
From: Mahesh Bandewar <mahesh@...dewar.net>
To: Jay Vosburgh <j.vosburgh@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
Veaceslav Falico <vfalico@...il.com>,
Nikolay Aleksandrov <nikolay@...hat.com>,
David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>
Cc: netdev <netdev@...r.kernel.org>,
Mahesh Bandewar <mahesh@...dewar.net>,
Mahesh Bandewar <maheshb@...gle.com>
Subject: [PATCH next 0/4] bonding: winter cleanup
From: Mahesh Bandewar <maheshb@...gle.com>
Few cleanup patches that I have accumulated over some time now.
(a) First two patches are basically to move the work-queue initialization
from every ndo_open / bond_open operation to once at the beginning while
port creation. Work-queue initialization is an unnecessary operation
for every 'ifup' operation. However we have some mode-specific work-queues
and mode can change anytime after port creation. So the second patch is
to ensure the correct work-handler is called based on the mode.
(b) Third patch is simple and straightforward that removes hard-coded value
that was added into the initial commit and replaces it with the default
value configured.
(c) The final patch in the series removes the unimplemented "port-moved" state
from the LACP state machine. This state is defined but never set so
removing from the state machine logic makes code little cleaner.
Note: None of these patches are making any functional changes.
Mahesh Bandewar (4):
bonding: restructure arp-monitor
bonding: initialize work-queues during creation of bond
bonding: remove hardcoded value
bonding: remove "port-moved" state that was never implemented
drivers/net/bonding/bond_3ad.c | 11 +++--------
drivers/net/bonding/bond_main.c | 42 ++++++++++++++++++++++++++++-------------
2 files changed, 32 insertions(+), 21 deletions(-)
--
2.11.0.483.g087da7b7c-goog
Powered by blists - more mailing lists