From: Stephen Hemminger <stephen@networkplumber.org>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] Techboard Minutes of Meeting - 10/8/2020
Date: Fri, 9 Oct 2020 09:30:52 -0700 [thread overview]
Message-ID: <20201009093052.0c31bab2@hermes.local> (raw)
In-Reply-To: <DBAPR08MB5814A768A09120774187B429980B0@DBAPR08MB5814.eurprd08.prod.outlook.com>
On Thu, 8 Oct 2020 23:37:50 +0000
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> wrote:
> d) LPM
> - Looks like other projects are using the LPM structure members, not just APIs.
> - AI: Honnappa: will take a closer look.
Thomas mentioned that LPM overlaps the functionality of FIB and RIB libraries.
Is there any plan to deprecate the older LPM libraries.
The RIB library has a better API. But it is slower for large number of routes.
LPM is a space/time tradeoff since it basically computes a full /24 table.
Perhaps DPDK could have one RIB API and different route table algorithms?
prev parent reply other threads:[~2020-10-09 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 23:37 Honnappa Nagarahalli
2020-10-09 16:30 ` Stephen Hemminger [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=20201009093052.0c31bab2@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=techboard@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).