From: "Kobylinski, MichalX" <michalx.kobylinski@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Increase number of next hops for LPM IPv4
Date: Tue, 8 Mar 2016 15:53:46 +0000 [thread overview]
Message-ID: <987EE72691933347B9F0B5C19E71B5BB1F04381C@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <5394159.7pQBa26eUn@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, March 8, 2016 4:13 PM
> To: Kobylinski, MichalX <michalx.kobylinski@intel.com>
> Cc: dev@dpdk.org; Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Subject: Re: [dpdk-dev] [PATCH v2 0/2] Increase number of next hops for
> LPM IPv4
> Importance: High
>
> 2016-01-29 13:12, Michal Kobylinski:
> > This patchset extend next_hop field from 8-bits to 24-bits in LPM library for
> IPv4.
>
> waiting v3, any news please?
I'm working on v3.
Today I will post v3 on mailing list.
> Jerin has to rebase on top of this series.
next prev parent reply other threads:[~2016-03-08 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 12:12 Michal Kobylinski
2016-01-29 12:12 ` [dpdk-dev] [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure Michal Kobylinski
2016-02-18 10:02 ` Hunt, David
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 ` [dpdk-dev] [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 ` [dpdk-dev] [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 [this message]
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=987EE72691933347B9F0B5C19E71B5BB1F04381C@IRSMSX101.ger.corp.intel.com \
--to=michalx.kobylinski@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).