From: Stephen Hemminger <stephen@networkplumber.org>
To: Medvedkin Vladimir <medvedkinv@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] Add RIB library
Date: Tue, 11 Jul 2017 13:31:43 -0700 [thread overview]
Message-ID: <20170711133143.77f02240@xeon-e3> (raw)
In-Reply-To: <1499801585-10031-1-git-send-email-medvedkinv@gmail.com>
On Tue, 11 Jul 2017 19:33:04 +0000
Medvedkin Vladimir <medvedkinv@gmail.com> wrote:
> Hi,
>
> I want to introduce new library for ip routing lookup that have some advantages
> over current LPM library. In short:
> - Increases the speed of control plane operations against lpm such as
> adding/deleting routes
> - Adds abstraction from dataplane algorythms, so it is possible to add
> different ip route lookup algorythms such as DXR/poptrie/lpc-trie/etc
> in addition to current dir24_8
> - It is possible to keep user defined application specific additional
> information in struct rte_rib_v4_node which represents route entry.
> It can be next hop/set of next hops (i.e. active and feasible),
> pointers to link rte_rib_v4_node based on some criteria (i.e. next_hop),
> plenty of additional control plane information.
> - For dir24_8 implementation it is possible to remove rte_lpm_tbl_entry.depth
> field that helps to save 6 bits.
> - Also new dir24_8 implementation supports different next_hop sizes
> (1/2/4/8 bytes per next hop)
>
> It would be nice to hear your opinion. The draft is below.
>
> Medvedkin Vladimir (1):
> lib/rib: Add Routing Information Base library
>
> config/common_base | 6 +
> doc/api/doxy-api.conf | 1 +
> lib/Makefile | 2 +
> lib/librte_rib/Makefile | 43 ++++
> lib/librte_rib/rte_dir24_8.c | 411 +++++++++++++++++++++++++++++++++++++++
> lib/librte_rib/rte_dir24_8.h | 144 ++++++++++++++
> lib/librte_rib/rte_rib.c | 454 +++++++++++++++++++++++++++++++++++++++++++
> lib/librte_rib/rte_rib.h | 260 +++++++++++++++++++++++++
> 8 files changed, 1321 insertions(+)
> create mode 100644 lib/librte_rib/Makefile
> create mode 100644 lib/librte_rib/rte_dir24_8.c
> create mode 100644 lib/librte_rib/rte_dir24_8.h
> create mode 100644 lib/librte_rib/rte_rib.c
> create mode 100644 lib/librte_rib/rte_rib.h
>
In network paralance a RIB is usually a full route table and FIB is the forwarding
table in use. You probably don't want to call this a RIB. It looks more like an
abstraction above FIB.
https://networkengineering.stackexchange.com/questions/38588/rib-vs-fib-differences
http://aftabsiddiqui.com/index.php/ip-routing-table-rib-and-forwarding-table-fib/
next prev parent reply other threads:[~2017-07-11 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 19:33 Medvedkin Vladimir
2017-07-11 19:33 ` [dpdk-dev] [PATCH] lib/rib: Add Routing Information Base library Medvedkin Vladimir
2017-07-11 20:28 ` Stephen Hemminger
2017-07-11 23:17 ` Vladimir Medvedkin
2017-07-11 20:31 ` Stephen Hemminger [this message]
2017-07-11 23:13 ` [dpdk-dev] [RFC] Add RIB library Vladimir Medvedkin
2017-08-14 10:51 ` Bruce Richardson
2017-08-14 22:28 ` Vladimir Medvedkin
2017-08-15 8:23 ` Bruce Richardson
2017-08-15 10:49 ` Vladimir Medvedkin
2017-08-15 11:01 ` Vladimir Medvedkin
2018-01-16 0:41 ` 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=20170711133143.77f02240@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=medvedkinv@gmail.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).