All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hunt, David" <david.hunt@intel.com>
To: Michal Kobylinski <michalx.kobylinski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure
Date: Thu, 18 Feb 2016 10:02:05 +0000	[thread overview]
Message-ID: <56C5969D.9040502@intel.com> (raw)
In-Reply-To: <1454069573-12059-2-git-send-email-michalx.kobylinski@intel.com>


On 1/29/2016 12:12 PM, Michal Kobylinski wrote:
> As next_hop field for IPv4 is increased now the maximum number of tbl8s is 2^24.
> A new rte_lpm_config structure is used so LPM library will allocate
> exactly the amount of memory which is necessary to hold application’s rules.
>
> Changed structures in LPM library:
> rte_lpm_tbl24_entry and rte_lpm_tbl8_entry to one structure
> rte_lpm_tbl_entry.
>
> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>

Acked-by: David Hunt<david.hunt@intel.com>

  reply	other threads:[~2016-02-18 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 12:12 [PATCH v2 0/2] Increase number of next hops for LPM IPv4 Michal Kobylinski
2016-01-29 12:12 ` [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure Michal Kobylinski
2016-02-18 10:02   ` Hunt, David [this message]
2016-03-02 15:28   ` Thomas Monjalon
2016-03-02 16:23     ` Kobylinski, MichalX
2016-03-02 16:35       ` Thomas Monjalon
2016-01-29 12:12 ` [PATCH 2/2] examples: update to use new lpm lib for ip4 Michal Kobylinski
2016-02-18 10:02   ` Hunt, David
2016-02-26  7:35 ` [PATCH v2 0/2] Increase number of next hops for LPM IPv4 Xu, HuilongX
2016-03-08 15:13 ` Thomas Monjalon
2016-03-08 15:53   ` Kobylinski, MichalX
2016-03-08 16:31     ` Thomas Monjalon
2016-03-08 21:00   ` Kobylinski, MichalX

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=56C5969D.9040502@intel.com \
    --to=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=michalx.kobylinski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.