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 for Android: free password hash cracker in your pocket

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

Message-Id: <20150321.221631.908834228517236497.davem@davemloft.net>
Date:	Sat, 21 Mar 2015 22:16:31 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	maheshb@...gle.com
Cc:	j.vosburgh@...il.com, andy@...yhouse.net, vfalico@...il.com,
	nikolay@...hat.com, maze@...gle.com, netdev@...r.kernel.org,
	edumazet@...gle.com
Subject: Re: [PATCH net-next v2 0/4] bonding work-queues, try_rtnl() &
 notifications

From: Mahesh Bandewar <maheshb@...gle.com>
Date: Sat, 21 Mar 2015 19:01:29 -0700

> I think you missed my earlier reply to your message. In summary, the
> notification deferral is 1ms which should not cause any trashing;
> more over with that suggested approach the rtnl-owner will have to
> do your job and will be subjected to the latencies which may be
> undesirable.

Someone has to do the work, and if the rtnl-owner does it we do not
incur all of the overhead the resubmission entails.

> OTOH this patch series is not adding any new deferral work, but just
> making it bug-free.

It's continuing a bad approach to the problem.
--
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