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
| ||
|
Date: Fri, 14 Jun 2019 18:42:08 +0000 From: Saeed Mahameed <saeedm@...lanox.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "pabeni@...hat.com" <pabeni@...hat.com> CC: "davem@...emloft.net" <davem@...emloft.net>, "leon@...nel.org" <leon@...nel.org> Subject: Re: [PATCH net-next v3 2/2] net/mlx5e: use indirect calls wrapper for the rx packet handler On Wed, 2019-06-12 at 12:18 +0200, Paolo Abeni wrote: > We can avoid another indirect call per packet wrapping the rx > handler call with the proper helper. > > To ensure that even the last listed direct call experience > measurable gain, despite the additional conditionals we must > traverse before reaching it, I tested reversing the order of the > listed options, with performance differences below noise level. > > Together with the previous indirect call patch, this gives > ~6% performance improvement in raw UDP tput. > > v2 -> v3: > - use only the direct calls always available regardless of > the mlx5 build options > - drop the direct call list macro, to keep the code as simple > as possible for future rework > > v1 -> v2: > - update the direct call list and use a macro to define it, > as per Saeed suggestion. An intermediated additional > macro is needed to allow arg list expansion > > Signed-off-by: Paolo Abeni <pabeni@...hat.com> > Acked-by: Saeed Mahameed <saeedm@...lanox.com>
Powered by blists - more mailing lists