2016-03-02 16:23, Kobylinski, MichalX:
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Sent: Wednesday, March 2, 2016 4:29 PM
> > Is it possible to split the changes in next_hop and config structure?
>
> It is possible. Do you mean to put config structure into seperate patch-set?
Hi,
As suggested by Bruce, I'm looking to apply this patchset before the ARM one.
Please check the comments below.
Is it possible to split the changes in next_hop and config structure?
> --- a/doc/guides/rel_notes/release_2_3.rst
> +++ b/doc/guides/rel_notes/release_2_3.rst
> @@ -18,7 +18,11 @@
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Wednesday, March 2, 2016 4:29 PM
> To: Kobylinski, MichalX
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 1/2] lpm: extend ip4 next_hop and add config
> structu
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 str
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_
5 matches
Mail list logo