From: Mahesh Bandewar <maheshb@google.com>
To: Jay Vosburgh <j.vosburgh@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Veaceslav Falico <vfalico@gmail.com>,
Nikolay Aleksandrov <nikolay@redhat.com>,
David Miller <davem@davemloft.net>
Cc: Mahesh Bandewar <maheshb@google.com>,
Maciej Zenczykowski <maze@google.com>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() & notifications
Date: Fri, 20 Mar 2015 22:39:15 -0700 [thread overview]
Message-ID: <1426916355-18289-1-git-send-email-maheshb@google.com> (raw)
This patch series tries to address the issue discovered in various work-
queues and the way these handlers deal with the RTNL. Especially for
notification handling. If RTNL can not be acquired, these handlers ignore
sending notifications and just re-arm the timer. This could be very
problematic if the re-arm timer has larger value (e.g. in minutes).
Mahesh Bandewar (4):
bonding: Handle notifications during work-queue processing gracefully
bonding: Do not ignore notifications for miimon-work-queue
bonding: Do not ignore notifications for AD-work-queue
bonding: Do not ignore notifications for ARP-work-queue
drivers/net/bonding/bond_3ad.c | 21 +++++++++++---
drivers/net/bonding/bond_main.c | 64 ++++++++++++++++++++++++-----------------
include/net/bonding.h | 19 ++++++++++++
3 files changed, 74 insertions(+), 30 deletions(-)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-03-21 5:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 5:39 Mahesh Bandewar [this message]
2015-03-21 22:17 ` [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() & notifications David Miller
2015-03-22 2:04 ` Mahesh Bandewar
[not found] ` <CAF2d9jhMz4Y1ye_ofkgvXyxUJEpNnLrFjMJhHQXKbf6MSS-OVg@mail.gmail.com>
2015-03-22 2:16 ` David Miller
2015-03-22 2:23 ` Maciej Żenczykowski
2015-03-22 2:36 ` David Miller
[not found] ` <CAF2d9jjgfPSoBHhvD20K+5i-3ty70+kpNPK8gqe-9HKVkrrVwQ@mail.gmail.com>
2015-03-22 8:20 ` Maciej Żenczykowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1426916355-18289-1-git-send-email-maheshb@google.com \
--to=maheshb@google.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=vfalico@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).