From: Brian Vazquez <brianvv@google.com>
To: Brian Vazquez <brianvv.kernel@gmail.com>,
Brian Vazquez <brianvv@google.com>,
Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next v2 0/4] net: avoid indirect calls in dst functions
Date: Fri, 11 Dec 2020 23:33:36 +0000 [thread overview]
Message-ID: <20201211233340.1503242-1-brianvv@google.com> (raw)
From: brianvv <brianvv@google.com>
Use of the indirect call wrappers in some dst related functions for the
ipv6/ipv4 case. This is a small improvent for CONFIG_RETPOLINE=y
Changed in v2:
-fix build issues reported by kernel test robot
brianvv (4):
net: use indirect call helpers for dst_input
net: use indirect call helpers for dst_output
net: use indirect call helpers for dst_mtu
net: indirect call helpers for ipv4/ipv6 dst_check functions
include/net/dst.h | 25 +++++++++++++++++++++----
net/core/sock.c | 12 ++++++++++--
net/ipv4/ip_input.c | 1 +
net/ipv4/ip_output.c | 1 +
net/ipv4/route.c | 13 +++++++++----
net/ipv4/tcp_ipv4.c | 5 ++++-
net/ipv6/ip6_output.c | 1 +
net/ipv6/route.c | 13 +++++++++----
net/ipv6/tcp_ipv6.c | 5 ++++-
9 files changed, 60 insertions(+), 16 deletions(-)
--
2.29.2.576.ga3fc446d84-goog
next reply other threads:[~2020-12-11 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 23:33 Brian Vazquez [this message]
2020-12-11 23:33 ` [PATCH net-next v2 1/4] net: use indirect call helpers for dst_input Brian Vazquez
2020-12-11 23:33 ` [PATCH net-next v2 2/4] net: use indirect call helpers for dst_output Brian Vazquez
2020-12-11 23:33 ` [PATCH net-next v2 3/4] net: use indirect call helpers for dst_mtu Brian Vazquez
2020-12-11 23:33 ` [PATCH net-next v2 4/4] net: indirect call helpers for ipv4/ipv6 dst_check functions Brian Vazquez
2020-12-15 3:27 ` [PATCH net-next v2 0/4] net: avoid indirect calls in dst functions Jakub Kicinski
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=20201211233340.1503242-1-brianvv@google.com \
--to=brianvv@google.com \
--cc=brianvv.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome