netdev - Re: [PATCH net-next v2 0/4] bonding work-queues, try

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANP3RGeVhFMSvToY7nTu06+eYyscJyHS=uEswnH9Wh=UNfMscQ@mail.gmail.com>
Date:	Sat, 21 Mar 2015 19:23:51 -0700
From:	Maciej Żenczykowski <maze@...gle.com>
To:	David Miller <davem@...emloft.net>
Cc:	Mahesh Bandewar <maheshb@...gle.com>,
	Jay Vosburgh <j.vosburgh@...il.com>,
	Andy Gospodarek <andy@...yhouse.net>,
	Veaceslav Falico <vfalico@...il.com>,
	Nikolay Aleksandrov <nikolay@...hat.com>,
	Linux NetDev <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() & notifications

> 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
?

(life might be easier if you can actually pass 2 args, but that's a
minor detail)

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();
}

- Maciej
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html