[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-30 Thread Matthew Hall
On Mon, Oct 26, 2015 at 11:40:46AM -0700, Matthew Hall wrote: > > I can't apply patch 0001-... , could You check it please? > > I generated it from a rebase of my own copy of DPDK against DPDK upstream > master. > > So I'm not sure why it would not apply against latest DPDK master. > > But I w

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-27 Thread Vladimir Medvedkin
Hi Michal, Try patch below. I will send it via git. Regards, Vladimir 2015-10-26 21:40 GMT+03:00 Matthew Hall : > > I can't apply patch 0001-... , could You check it please? > > I generated it from a rebase of my own copy of DPDK against DPDK upstream > master. > > So I'm not sure why it would

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-27 Thread Vladimir Medvedkin
Signed-off-by: Vladimir Medvedkin --- config/common_bsdapp | 1 + config/common_linuxapp | 1 + lib/librte_lpm/rte_lpm.c | 194 +-- lib/librte_lpm/rte_lpm.h | 163 +++ 4 files changed, 219 insertions(+), 140

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Vladimir Medvedkin
uint8_t next_hop; >}; > }; > > struct rte_lpm_tbl8_entry { >uint8_t depth :6; >uint8_t valid_group :1; >uint8_t valid :1; >uint8_t next_hop; > }; > #endif > > /** @internal Rule structure. */ > struct rte_lp

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Vladimir Medvedkin
t intel.com] > > Sent: Monday, October 26, 2015 12:55 PM > > To: Vladimir Medvedkin > > Subject: Re: [dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops > > for lpm (ipv4) > > > > On Sun, Oct 25, 2015 at 08:52:04PM +0300, Vladimir Medvedkin wrote: > &g

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Michal Jastrzebski
/rte_lpm.h:81 error: lib/librte_lpm/rte_lpm.h: patch does not apply > 2015-10-26 14:57 GMT+03:00 Jastrzebski, MichalX K < > michalx.k.jastrzebski at intel.com>: > > > > -Original Message- > > > From: Michal Jastrzebski [mailto:michalx.k.jastrzebski at intel.com] > &

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Jastrzebski, MichalX K
> -Original Message- > From: Matthew Hall [mailto:mhall at mhcomputing.net] > Sent: Saturday, October 24, 2015 8:10 AM > To: Jastrzebski, MichalX K; Kobylinski, MichalX > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops > f

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Jastrzebski, MichalX K
> -Original Message- > From: Michal Jastrzebski [mailto:michalx.k.jastrzebski at intel.com] > Sent: Monday, October 26, 2015 12:55 PM > To: Vladimir Medvedkin > Subject: Re: [dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops > for lpm (ipv4) > > On Sun, Oc

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-26 Thread Matthew Hall
> I can't apply patch 0001-... , could You check it please? I generated it from a rebase of my own copy of DPDK against DPDK upstream master. So I'm not sure why it would not apply against latest DPDK master. But I will try it and see what could be the reason. Matthew.

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-25 Thread Vladimir Medvedkin
Hi all, Here my implementation Signed-off-by: Vladimir Medvedkin --- config/common_bsdapp | 1 + config/common_linuxapp | 1 + lib/librte_lpm/rte_lpm.c | 194 +-- lib/librte_lpm/rte_lpm.h | 163 +++ 4 file

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Matthew Hall
On 10/23/15 9:20 AM, Matthew Hall wrote: > On Fri, Oct 23, 2015 at 03:51:48PM +0200, Michal Jastrzebski wrote: >> From: Michal Kobylinski >> >> The current DPDK implementation for LPM for IPv4 and IPv6 limits the >> number of next hops to 256, as the next hop ID is an 8-bit long field. >> Propose

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Vladimir Medvedkin
Hi all, I also have LPM library implementation. Main points: - First, we don't need two separate structures rte_lpm_tbl8_entry and rte_lpm_tbl24_entry. I think it's better to merge in one rte_lpm_tbl_entry because there is only one difference in name of one bit - valid_group vs ext_entry. Let it's

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Michal Jastrzebski
From: Michal Kobylinski The current DPDK implementation for LPM for IPv4 and IPv6 limits the number of next hops to 256, as the next hop ID is an 8-bit long field. Proposed extension increase number of next hops for IPv4 to 2^24 and also allows 32-bits read/write operations. This patchset requi

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Stephen Hemminger

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Matthew Hall
On Fri, Oct 23, 2015 at 09:33:05AM -0700, Stephen Hemminger wrote: > On Fri, 23 Oct 2015 09:20:33 -0700 > Matthew Hall wrote: > > > On Fri, Oct 23, 2015 at 03:51:48PM +0200, Michal Jastrzebski wrote: > > > From: Michal Kobylinski > > > > > > The current DPDK implementation for LPM for IPv4 and

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Stephen Hemminger
On Fri, 23 Oct 2015 09:20:33 -0700 Matthew Hall wrote: > On Fri, Oct 23, 2015 at 03:51:48PM +0200, Michal Jastrzebski wrote: > > From: Michal Kobylinski > > > > The current DPDK implementation for LPM for IPv4 and IPv6 limits the > > number of next hops to 256, as the next hop ID is an 8-bit l

[dpdk-dev] [PATCH v1 0/3] lpm: increase number of next hops for lpm (ipv4)

2015-10-23 Thread Matthew Hall
On Fri, Oct 23, 2015 at 03:51:48PM +0200, Michal Jastrzebski wrote: > From: Michal Kobylinski > > The current DPDK implementation for LPM for IPv4 and IPv6 limits the > number of next hops to 256, as the next hop ID is an 8-bit long field. > Proposed extension increase number of next hops for IP