From: David Miller <davem@davemloft.net>
To: brianvv@google.com
Cc: brianvv.kernel@gmail.com, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lkp@intel.com
Subject: Re: [PATCH V2 net-next] fib: use indirect call wrappers in the most common fib_rules_ops
Date: Tue, 28 Jul 2020 17:43:20 -0700 (PDT) [thread overview]
Message-ID: <20200728.174320.263367752875525504.davem@davemloft.net> (raw)
In-Reply-To: <20200726224816.1819557-1-brianvv@google.com>
From: Brian Vazquez <brianvv@google.com>
Date: Sun, 26 Jul 2020 15:48:16 -0700
> This avoids another inderect call per RX packet which save us around
> 20-40 ns.
>
> Changelog:
>
> v1 -> v2:
> - Move declaraions to fib_rules.h to remove warnings
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Brian Vazquez <brianvv@google.com>
Applied, thank you.
prev parent reply other threads:[~2020-07-29 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 22:48 [PATCH V2 net-next] fib: use indirect call wrappers in the most common fib_rules_ops Brian Vazquez
2020-07-29 0:43 ` David Miller [this message]
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=20200728.174320.263367752875525504.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brianvv.kernel@gmail.com \
--cc=brianvv@google.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).