From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/2] small RIB optimizations
Date: Tue, 12 Apr 2022 19:09:32 -0700 [thread overview]
Message-ID: <20220413020935.90499-1-stephen@networkplumber.org> (raw)
A couple of small micro optimizations on the RIB code.
Stephen Hemminger (2):
rib: mark error checks with unlikely
rib6: mark error tests with unlikely
lib/rib/rte_rib.c | 26 +++++++++++++-------------
lib/rib/rte_rib6.c | 25 ++++++++++++-------------
2 files changed, 25 insertions(+), 26 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-13 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 2:09 Stephen Hemminger [this message]
2022-04-13 2:09 ` [PATCH 1/2] rib: mark error checks with unlikely Stephen Hemminger
2022-04-26 14:27 ` Medvedkin, Vladimir
2022-04-13 2:09 ` [PATCH 2/2] rib6: mark error tests " Stephen Hemminger
2022-04-26 14:27 ` Medvedkin, Vladimir
2022-04-13 6:45 ` [PATCH 0/2] small RIB optimizations Morten Brørup
2022-06-01 8:58 ` Thomas Monjalon
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=20220413020935.90499-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).