From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@mellanox.com>,
Leon Romanovsky <leon@kernel.org>
Subject: [PATCH net-next 0/3] net/mlx5: use indirect call wrappers
Date: Fri, 31 May 2019 14:53:32 +0200 [thread overview]
Message-ID: <cover.1559304330.git.pabeni@redhat.com> (raw)
The mlx5_core driver uses several indirect calls in fast-path, some of them
are invoked on each ingress packet, even for the XDP-only traffic.
This series leverage the indirect call wrappers infrastructure the avoid
the expansive RETPOLINE overhead for 2 indirect calls in fast-path.
Each call is addressed on a different patch, plus we need to introduce a couple
of additional helpers to cope with the higher number of possible direct-call
alternatives.
Paolo Abeni (3):
net/mlx5e: use indirect calls wrapper for skb allocation
indirect call wrappers: add helpers for 3 and 4 ways switch
net/mlx5e: use indirect calls wrapper for the rx packet handler
.../net/ethernet/mellanox/mlx5/core/en_rx.c | 26 ++++++++++++++-----
include/linux/indirect_call_wrapper.h | 12 +++++++++
2 files changed, 32 insertions(+), 6 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-31 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 12:53 Paolo Abeni [this message]
2019-05-31 12:53 ` [PATCH net-next 1/3] net/mlx5e: use indirect calls wrapper for skb allocation Paolo Abeni
2019-05-31 12:53 ` [PATCH net-next 2/3] indirect call wrappers: add helpers for 3 and 4 ways switch Paolo Abeni
2019-05-31 18:30 ` Saeed Mahameed
2019-06-03 9:51 ` Paolo Abeni
2019-06-03 22:27 ` Saeed Mahameed
2019-06-05 8:35 ` Paolo Abeni
2019-05-31 12:53 ` [PATCH net-next 3/3] net/mlx5e: use indirect calls wrapper for the rx packet handler Paolo Abeni
2019-05-31 18:41 ` Saeed Mahameed
2019-06-03 9:55 ` Paolo Abeni
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=cover.1559304330.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.