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 v3 0/2] Increased number of next hops for LPM IPv4
Date: Wed, 9 Mar 2016 09:28:17 +0000 [thread overview]
Message-ID: <987EE72691933347B9F0B5C19E71B5BB1F043BF9@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1679909.QS6PQFfjcW@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, March 9, 2016 1:42 AM
> To: Kobylinski, MichalX <michalx.kobylinski@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 0/2] Increased number of next hops for
> LPM IPv4
> Importance: High
>
> 2016-03-08 21:52, Michal Kobylinski:
> > This patchset extended next_hop field from 8-bits to 24-bits in LPM library
> for IPv4.
> >
> > Added versioning symbols to functions and updated library and
> > applications that have a dependency on LPM library.
> >
> > Michal Kobylinski (2):
> > lpm: extend ip4 next_hop and add config structure
> > examples: update to use new lpm lib for ipv4
>
> You cannot split library and apps in such change because each commit must
> compile (including the examples).
Ok, I will merge my changes and I will send next version.
I split my patchset because I thought it will be better to review for community.
next prev parent reply other threads:[~2016-03-09 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 20:52 Michal Kobylinski
2016-03-08 20:52 ` [dpdk-dev] [PATCH v3 1/2] lpm: extended ipv4 next_hop field Michal Kobylinski
2016-03-08 20:52 ` [dpdk-dev] [PATCH 2/2] examples: update to use new lpm lib for ipv4 Michal Kobylinski
2016-03-09 0:45 ` Thomas Monjalon
2016-03-09 0:42 ` [dpdk-dev] [PATCH v3 0/2] Increased number of next hops for LPM IPv4 Thomas Monjalon
2016-03-09 9:28 ` Kobylinski, MichalX [this message]
2016-03-09 12:40 ` [dpdk-dev] [PATCH v4] lpm: extended ipv4 next_hop field Michal Jastrzebski
2016-03-09 13:39 ` Thomas Monjalon
2016-03-09 16:57 ` [dpdk-dev] [PATCH v5 0/2] Increased number of next hops for LPM IPv4 Michal Jastrzebski
2016-03-09 16:57 ` [dpdk-dev] [PATCH v5 1/2] lpm: extended ipv4 next_hop field Michal Jastrzebski
2016-03-09 16:57 ` [dpdk-dev] [PATCH v5 2/2] lpm: added a new rte_lpm_config structure for ipv4 Michal Jastrzebski
2016-03-09 22:09 ` [dpdk-dev] [PATCH v5 0/2] Increased number of next hops for LPM IPv4 Thomas Monjalon
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=987EE72691933347B9F0B5C19E71B5BB1F043BF9@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).