From: Ivan Boule <ivan.boule@6wind.com>
To: "Wang, Shawn" <xingbow@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] question about PKT_RX_IPV4_HDR_EXT
Date: Mon, 06 Jan 2014 16:27:04 +0100 [thread overview]
Message-ID: <52CACB48.7020100@6wind.com> (raw)
In-Reply-To: <CEE1E3CB.41AA0%xingbow@amazon.com>
On 12/26/2013 10:46 PM, Wang, Shawn wrote:
> Hi:
>
> Can anyone explain more details about the rte_mbuf ol_flag : PKT_RX_IPV4_HDR_EXT?
> The document said “RX packet with extended IPv4 header.”
> But what is the extended IPv4 header looks like? What is the difference with normal IPv4 header?
> Can anyone give me an example?
>
> Thanks a lot.
> Wang, Shawn
Hi,
A extended IPv4 header is a IPv4 header with additional options, whose
total header size is greater than 20 bytes. Intel 1GbE and 10Gbe
Ethernet controllers are able to recognize such packets, and, in this
case,set a
dedicated flag into the RX descriptor where they store the packet.
Then, to supply this hardware-detected packet characteristics to the
upper-level application,
the RX functions of DPDK PollMode Drivers of the 1GbE and 10Gbe Ethernet
controllers set the
PKT_RX_IPV4_HDR_EXT generic flag into the mbuf that contains the packet.
Best regards,
Ivan
--
Ivan Boule
6WIND Development Engineer
prev parent reply other threads:[~2014-01-06 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 21:46 Wang, Shawn
2014-01-06 15:27 ` Ivan Boule [this message]
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=52CACB48.7020100@6wind.com \
--to=ivan.boule@6wind.com \
--cc=dev@dpdk.org \
--cc=xingbow@amazon.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).