DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Martin Drašar" <drasar@ics.muni.cz>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Removal of IP version from packet offload feature flags
Date: Mon, 31 Aug 2015 10:56:36 +0200	[thread overview]
Message-ID: <4354342.IqQZSKtSMX@xps13> (raw)
In-Reply-To: <55E40A4F.3030406@ics.muni.cz>

2015-08-31 10:03, Martin Drašar:
> I just tried to upgrade to 2.1.0 and suddenly my code stopped compiling,
> because of using PKT_RX_IPV4_HDR feature flag and the like. In the
> rte_mbuf.h there is this code:
> 
> > #ifndef RTE_NEXT_ABI
> > #define PKT_RX_IPV4_HDR      (1ULL << 5)  /**< RX packet with IPv4 header. */
> > #define PKT_RX_IPV4_HDR_EXT  (1ULL << 6)  /**< RX packet with extended IPv4 header. */
> > #define PKT_RX_IPV6_HDR      (1ULL << 7)  /**< RX packet with IPv6 header. */
> > #define PKT_RX_IPV6_HDR_EXT  (1ULL << 8)  /**< RX packet with extended IPv6 header. */
> > #endif /* RTE_NEXT_ABI */

In order to keep compatibility with your old code, you have to disable
RTE_NEXT_ABI in your configuration file (.config).

> So I guess that means the code got deprecated between 2.0.0 and 2.1.0,
> although I did not find relevant comment in the changelog. My question
> is, what should I use instead and even better - why was this change made?

See "Extended packet type support" in
	http://dpdk.org/doc/guides/rel_notes/release_2_1.html
and
	http://dpdk.org/doc/guides/rel_notes/deprecation.html

  reply	other threads:[~2015-08-31  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  8:03 Martin Drašar
2015-08-31  8:56 ` Thomas Monjalon [this message]
     [not found]   ` <55E42F25.4020406@ics.muni.cz>
2015-08-31 12:22     ` Thomas Monjalon
2015-08-31 12:47       ` Martin Drašar

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=4354342.IqQZSKtSMX@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=drasar@ics.muni.cz \
    /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).