From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>,
"Liu, Jijiang" <jijiang.liu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] mbuf:add two TX offload flags and change three fields
Date: Mon, 1 Dec 2014 11:58:36 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258213BBB21@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <547C3A43.8020009@6wind.com>
> -----Original Message-----
> From: Olivier MATZ [mailto:olivier.matz@6wind.com]
> Sent: Monday, December 01, 2014 9:52 AM
> To: Liu, Jijiang; Ananyev, Konstantin
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 1/3] mbuf:add two TX offload flags and change three fields
>
> Hi Jijiang,
>
> On 12/01/2014 03:30 AM, Liu, Jijiang wrote:
> >> After another thought, I think that the way you proposed is a better one.
> >> I gives us more flexibility:
> >> let's say for now we'll keep both l2_len and outer_l2_len as 7 bit fields, and upper
> >> layer would have to:
> >> mb->l2_len = eth_hdr_in + vxlan_hdr;
> >
> > A question, how to fill the mb->l2_len for IP in IP, IP in GRE tunneling packet that is no inner L2 header?
> > What is the rule?
> > Or you think it should be mb->l2_len = 0 + l4_tun_len; ??
I think it should be:
l2_len = 0 + l4_tun_len;
>From your patch:
l4_tunnel_len = l4_tun_len + l2_len;
>
> We could have the following rule:
> - the l2_len starts after the end of outer_l2_len + outer_l3_len (if
> they are not 0)
I think it should start after the outer_l4_hdr.
I.e. right now we don't include udp header length into it.
> - l2_len is the length of all headers up to the first ip or ipv6
> header
Yes, same thought here.
>
> Examples:
>
> Ether/IP/UDP/xxx
> m->outer_l2_len = 0
> m->outer_l3_len = 0
> m->l2_len = sizeof(ether)
> m->l3_len = sizeof(ip)
> m->l4_len = sizeof(udp)
>
> Ether/IP/IP/UDP/xxx
> m->outer_l2_len = sizeof(ether)
> m->outer_l3_len = sizeof(ip)
> m->l2_len = 0
> m->l3_len = sizeof(ip)
> m->l4_len = sizeof(udp)
>
> Ether/IP/GRE/IP/UDP/xxx
> m->outer_l2_len = sizeof(ether)
> m->outer_l3_len = sizeof(ip)
> m->l2_len = sizeof(gre)
> m->l3_len = sizeof(ip)
> m->l4_len = sizeof(udp)
>
> Ether/IP/UDP/vxlan/Ether/IP/UDP/xxx
> m->outer_l2_len = sizeof(ether)
> m->outer_l3_len = sizeof(ip)
> m->l2_len = sizeof(udp) + sizeof(vxlan) + sizeof(ether)
I think it should be:
m->l2_len = sizeof(vxlan) + sizeof(ether)
We don't need to add sizeof(udp) as we already say to the HW that I t will be UDP TUNNELING vi the ol_flag: PKT_TX_UDP_TUNNEL_PKT.
> m->l3_len = sizeof(ip)
> m->l4_len = sizeof(udp)
>
> Regards,
> Olivier
next prev parent reply other threads:[~2014-12-01 11:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 8:18 [dpdk-dev] [PATCH 0/3] i40e VXLAN TX checksum rework Jijiang Liu
2014-11-27 8:18 ` [dpdk-dev] [PATCH 1/3] mbuf:add two TX offload flags and change three fields Jijiang Liu
2014-11-27 10:00 ` Olivier MATZ
2014-11-27 13:14 ` Liu, Jijiang
2014-11-28 9:17 ` Olivier MATZ
[not found] ` <1ED644BD7E0A5F4091CF203DAFB8E4CC01D9EEA0@SHSMSX101.ccr.corp.intel.com>
2014-11-27 14:56 ` Ananyev, Konstantin
2014-11-27 17:01 ` Ananyev, Konstantin
2014-11-28 10:45 ` Olivier MATZ
2014-11-28 11:16 ` Ananyev, Konstantin
2014-11-30 14:50 ` Ananyev, Konstantin
2014-12-01 2:30 ` Liu, Jijiang
2014-12-01 9:52 ` Olivier MATZ
2014-12-01 11:58 ` Ananyev, Konstantin [this message]
2014-12-01 12:28 ` Olivier MATZ
2014-12-01 13:07 ` Liu, Jijiang
2014-12-01 14:31 ` Ananyev, Konstantin
2014-11-27 8:18 ` [dpdk-dev] [PATCH 2/3] i40e:PMD change for VXLAN TX checksum Jijiang Liu
2014-11-27 8:18 ` [dpdk-dev] [PATCH 3/3] testpmd:rework csum forward engine Jijiang Liu
2014-11-27 10:23 ` Olivier MATZ
2014-11-27 8:50 ` [dpdk-dev] [PATCH 0/3] i40e VXLAN TX checksum rework Liu, Jijiang
2014-11-27 9:44 ` Olivier MATZ
2014-11-27 10:12 ` Olivier MATZ
2014-11-27 12:06 ` Liu, Jijiang
2014-11-27 12:07 ` Liu, Jijiang
2014-11-27 15:29 ` Ananyev, Konstantin
2014-11-27 16:31 ` Liu, Jijiang
2014-12-03 8:02 ` Liu, Jijiang
2014-11-28 9:26 ` Olivier MATZ
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=2601191342CEEE43887BDE71AB977258213BBB21@IRSMSX105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=jijiang.liu@intel.com \
--cc=olivier.matz@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).