[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160718.220342.805963245855552246.davem@davemloft.net>
Date:	Mon, 18 Jul 2016 22:03:42 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kan.liang@...el.com
Cc:	hannes@...essinduktion.org, andi@...stfloor.org, fw@...len.de,
	linux-kernel@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
	netdev@...r.kernel.org, jeffrey.t.kirsher@...el.com,
	mingo@...hat.com, peterz@...radead.org, kuznet@....inr.ac.ru,
	jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net,
	akpm@...ux-foundation.org, keescook@...omium.org,
	viro@...iv.linux.org.uk, gorcunov@...nvz.org,
	john.stultz@...aro.org, aduyck@...antis.com, ben@...adent.org.uk,
	decot@...glers.com, jesse.brandeburg@...el.com
Subject: Re: [RFC PATCH 00/30] Kernel NET policy
From: "Liang, Kan" <kan.liang@...el.com>
Date: Tue, 19 Jul 2016 01:49:41 +0000
> Yes, rtnl will bring some overheads. But the configuration is one
> time thing for application or socket. It only happens on receiving
> first packet.
Thanks for destroying our connection rates.
This kind of overhead is simply unacceptable.
Powered by blists - more mailing lists
 
