From: David Marchand <david.marchand@redhat.com>
To: "Warrington, Jeffrey" <jwarrington@verisign.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Julien Charbon <jcharbon@verisign.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v2] lpm: improve performance with copious IPv4 peering routes
Date: Fri, 10 Nov 2023 08:42:03 +0100 [thread overview]
Message-ID: <CAJFAV8xRHJYm2_AR9hiYaBKUJBMHQSj18aNAxiNpj=HqYL-COQ@mail.gmail.com> (raw)
In-Reply-To: <0d975b44d6d443abaa00c02a1967c6b7@verisign.com>
Hello Jeffrey,
On Fri, Nov 10, 2023 at 12:11 AM Warrington, Jeffrey
<jwarrington@verisign.com> wrote:
>
> Minimize the performance impact of large numbers of BGP peering
> routes by updating LPM's IPv4 code to use a hash like the IPv6 code.
>
> Co-authored-by: Julien Charbon <jcharbon@verisign.com>
> Signed-off-by: Julien Charbon <jcharbon@verisign.com>
> Signed-off-by: Jeff Warrington <jwarrington@verisign.com>
> Co-authored-by: Nicolas Witkowski <nwitkowski@verisign.com>
> Signed-off-by: Nicolas Witkowski <nwitkowski@verisign.com>
> Co-authored-by: Rohit Gupta <rogupta@verisign.com>
> Signed-off-by: Rohit Gupta <rogupta@verisign.com>
Thanks for the patch.
Cc: lpm maintainers.
Don't forget to Cc: maintainers when sending patches.
You can simply pass --cc-cmd devtools/get-maintainer.sh to git send-email.
Can you provide performance numbers?
After this patch, LPM and LPM6 implementations become close.
Did you consider refactoring so that LPM and LPM6 can share more code?
> ---
> lib/lpm/rte_lpm.c | 306 ++++++++++++++++++++++------------------------
> lib/lpm/rte_lpm.h | 6 +
Seeing how no other .c is touched and no exposed symbol use it,
exposing the rte_lpm_rule_key structure in the public API is unneeded.
> 2 files changed, 149 insertions(+), 163 deletions(-)
--
David Marchand
next prev parent reply other threads:[~2023-11-10 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 23:11 Warrington, Jeffrey
2023-11-10 7:42 ` David Marchand [this message]
2023-11-10 14:08 Warrington, Jeffrey
2023-11-10 17:27 ` Medvedkin, Vladimir
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='CAJFAV8xRHJYm2_AR9hiYaBKUJBMHQSj18aNAxiNpj=HqYL-COQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jcharbon@verisign.com \
--cc=jwarrington@verisign.com \
--cc=vladimir.medvedkin@intel.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).