From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>,
"Liu, Jijiang" <jijiang.liu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/4] mbuf:add three TX offload flags and change three fields
Date: Fri, 28 Nov 2014 10:27:34 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258213BB1EA@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <54784232.8030707@6wind.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ
> Sent: Friday, November 28, 2014 9:37 AM
> To: Liu, Jijiang; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 1/4] mbuf:add three TX offload flags and change three fields
>
> Hi Jijiang,
>
> On 11/27/2014 06:03 PM, Jijiang Liu wrote:
> > /** Tell the NIC it's an IPv4 packet. Required for L4 checksum offload or TSO. */
> > #define PKT_TX_IPV4 PKT_RX_IPV4_HDR
> >
> > /** Tell the NIC it's an IPv6 packet. Required for L4 checksum offload or TSO. */
> > #define PKT_TX_IPV6 PKT_RX_IPV6_HDR
>
> The description still does not match what we discussed. Either we
> have PKT_TX_IPV4 meaning "packet is IPv4 without requiring IP cksum
> offload", or "packet is IPv4". I prefer the second one, but whatever
> the choice is, the comments must be coherent.
>
> > -#define PKT_TX_VLAN_PKT (1ULL << 55) /**< TX packet is a 802.1q VLAN packet. */
> > +/** Outer IP cksum of TX pkt. computed by NIC for tunneling packet */
> > +#define PKT_TX_OUTER_IP_CKSUM (1ULL << 58)
> > +
> > +/** Tell the NIC it's an outer IPv6 packet for tunneling packet.*/
> > +#define PKT_TX_OUTER_IPV6 (1ULL << 59)
>
> I think we should have the same flags with the same meanings for
> inner and outer:
>
> - PKT_TX_IPV4, PKT_TX_IP_CKSUM, PKT_TX_IPV6
> - PKT_TX_OUTER_IPV4, PKT_TX_OUTER_IP_CKSUM, PKT_TX_OUTER_IPV6
Good point.
I still think: should we squeeze each of these triple in 2 bits?
Same as we doing for L4 checksum flags:
#define PKT_TX_IP_CKSUM (1ULL << X)
#define PKT_TX_IPV6 (2ULL << X)
#define PKT_TX_IPV4 (3ULL << X)
Same of outer flags.
Of course it means that they need to be mutually exclusive.
>
> In your patch there is no PKT_TX_OUTER_IPV4 flag.
>
> Regards,
> Olivier
next prev parent reply other threads:[~2014-11-28 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 17:03 [dpdk-dev] [PATCH v3 0/4] i40e VXLAN TX checksum rework Jijiang Liu
2014-11-27 17:03 ` [dpdk-dev] [PATCH v3 1/4] mbuf:add three TX offload flags and change three fields Jijiang Liu
2014-11-28 9:36 ` Olivier MATZ
2014-11-28 10:27 ` Ananyev, Konstantin [this message]
2014-11-28 10:33 ` Liu, Jijiang
2014-11-28 10:40 ` Ananyev, Konstantin
2014-11-28 11:00 ` Olivier MATZ
2014-11-28 11:13 ` Ananyev, Konstantin
2014-11-28 11:18 ` Olivier MATZ
2014-11-28 15:46 ` Ananyev, Konstantin
2014-11-27 17:03 ` [dpdk-dev] [PATCH v3 2/4] mbuf:change PKT_TX_IPV4 and PKT_TX_IPV6 definition Jijiang Liu
2014-11-28 9:37 ` Olivier MATZ
2014-11-27 17:03 ` [dpdk-dev] [PATCH v3 3/4] i40e:PMD change for VXLAN TX checksum Jijiang Liu
2014-11-27 17:03 ` [dpdk-dev] [PATCH v3 4/4] testpmd:rework csum forward engine Jijiang Liu
2014-11-28 9:50 ` Olivier MATZ
2014-11-28 10:10 ` Thomas Monjalon
2014-11-27 17:24 ` [dpdk-dev] [PATCH v3 0/4] i40e VXLAN TX checksum rework Ananyev, Konstantin
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=2601191342CEEE43887BDE71AB977258213BB1EA@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).