DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_lpm with larger nexthops or another method?
Date: Mon, 22 Jun 2015 23:51:02 -0400	[thread overview]
Message-ID: <20150622235102.41c3619a@uryu.home.lan> (raw)
In-Reply-To: <20150622175302.GA15788@mhcomputing.net>

In order to make Vyatta/Brocade router work with LPM code
I ended up redoing the layout. It is:


/** Tbl24 entry structure. */
struct rte_lpm_tbl24_entry {
	/* Using single uint8_t to store 3 values. */
	uint8_t valid       :1; /**< Validation flag. */
	uint8_t ext_entry   :1; /**< external entry? */
	uint8_t depth;	      /**< Rule depth. */
	/* Stores Next hop or group index (i.e. gindex)into tbl8. */
	union {
		uint16_t next_hop;
		uint16_t tbl8_gindex;
	};
};

/** Tbl8 entry structure. */
struct rte_lpm_tbl8_entry {
	uint16_t next_hop;	/**< next hop. */
	uint8_t  depth;	/**< Rule depth. */
	uint8_t valid       :1; /**< Validation flag. */
	uint8_t valid_group :1; /**< Group validation flag. */
};

And also several other scalability improvements (plus IPv6)
and the correct handling of /32.

Unfortunately, this is such a big binary change that I was
reluctant to break any tests or applications using existing code
and therefore never submitted the patches.

  reply	other threads:[~2015-06-23  3:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  2:29 Matthew Hall
2015-06-22 10:11 ` Vladimir Medvedkin
2015-06-22 17:53   ` Matthew Hall
2015-06-23  3:51     ` Stephen Hemminger [this message]
2015-06-23  6:30       ` Matthew Hall
2015-06-23  7:19         ` Vladimir Medvedkin
2015-06-24  4:13           ` Matthew Hall
2015-06-24  4:28             ` Matthew Hall
2015-06-24  5:15               ` Matthew Hall
2015-06-24  7:04                 ` Vladimir Medvedkin
2015-06-24 17:56                   ` Matthew Hall
2015-06-26  7:01                     ` Matthew Hall

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=20150622235102.41c3619a@uryu.home.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).