From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Kobylinski <michalx.kobylinski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/2] Increased number of next hops for LPM IPv4
Date: Wed, 09 Mar 2016 01:42:24 +0100 [thread overview]
Message-ID: <1679909.QS6PQFfjcW@xps13> (raw)
In-Reply-To: <1457470323-26368-1-git-send-email-michalx.kobylinski@intel.com>
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).
next prev parent reply other threads:[~2016-03-09 0:44 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 ` Thomas Monjalon [this message]
2016-03-09 9:28 ` [dpdk-dev] [PATCH v3 0/2] Increased number of next hops for LPM IPv4 Kobylinski, MichalX
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=1679909.QS6PQFfjcW@xps13 \
--to=thomas.monjalon@6wind.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 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).