From: David Miller <davem@davemloft.net>
To: maze@google.com
Cc: maheshb@google.com, j.vosburgh@gmail.com, andy@greyhouse.net,
vfalico@gmail.com, nikolay@redhat.com, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() & notifications
Date: Sat, 21 Mar 2015 22:36:37 -0400 (EDT) [thread overview]
Message-ID: <20150321.223637.2214520794734249959.davem@davemloft.net> (raw)
In-Reply-To: <CANP3RGeVhFMSvToY7nTu06+eYyscJyHS=uEswnH9Wh=UNfMscQ@mail.gmail.com>
From: Maciej Żenczykowski <maze@google.com>
Date: Sat, 21 Mar 2015 19:23:51 -0700
>> Someone has to do the work, and if the rtnl-owner does it we do not
>> incur all of the overhead the resubmission entails.
>
> Are you suggesting:
> - adding a global queue of (function pointer, long arg)
> - changing rtnl_unlock to iterate through the queue calling
> function(arg) before it actually releases the rtnl lock
> ?
Something like that.
> I guess at that point you could even have a generic method
>
> void asynch_call_under_rtnl(function, arg) {
> rtnl_callback_add_to_queue(function,arg)
> if (rtnl_try_lock())
> rtnl_unlock();
> }
Right.
next prev parent reply other threads:[~2015-03-22 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 5:39 [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() & notifications Mahesh Bandewar
2015-03-21 22:17 ` 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 [this message]
[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=20150321.223637.2214520794734249959.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.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).