DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Jijiang Liu <jijiang.liu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 7/8]i40e:support VxLAN Tx checksum offload
Date: Mon, 29 Sep 2014 11:50:55 +0100	[thread overview]
Message-ID: <20140929105055.GE12072@BRICHA3-MOBL> (raw)
In-Reply-To: <1411696929-13856-8-git-send-email-jijiang.liu@intel.com>

On Fri, Sep 26, 2014 at 10:02:08AM +0800, Jijiang Liu wrote:
> Support VxLAN Tx checksum offload, which include
>   - outer L3(IP) checksum offload
>   - inner L3(IP) checksum offload
>   - inner L4(UDP, TCP and SCTP) checksum offload
>  
> Signed-off-by: Jijiang Liu <jijiang.liu@intel.com>
> Acked-by: Helin Zhang <helin.zhang@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> Acked-by: Jing Chen <jing.d.chen@intel.com>
> 
> ---
>  lib/librte_mbuf/rte_mbuf.h        |    2 +
>  lib/librte_pmd_i40e/i40e_ethdev.c |    4 +-
>  lib/librte_pmd_i40e/i40e_rxtx.c   |   47 ++++++++++++++++++++++++++++++++++--
>  3 files changed, 48 insertions(+), 5 deletions(-)
> 
> diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
> index 4955684..1f3f4eb 100644
> --- a/lib/librte_mbuf/rte_mbuf.h
> +++ b/lib/librte_mbuf/rte_mbuf.h
> @@ -86,6 +86,8 @@ extern "C" {
>  #define PKT_RX_IEEE1588_PTP  0x0200 /**< RX IEEE1588 L2 Ethernet PT Packet. */
>  #define PKT_RX_IEEE1588_TMST 0x0400 /**< RX IEEE1588 L2/L4 timestamped packet.*/
>  
> +#define PKT_TX_VXLAN_CKSUM   0x0001 /**< Checksum of TX VxLAN pkt. computed by NIC.. */
> +#define PKT_TX_IVLAN_PKT     0x0002 /**< TX packet is VxLAN packet with an inner VLAN. */
>  #define PKT_TX_VLAN_PKT      0x0800 /**< TX packet is a 802.1q VLAN packet. */
>  #define PKT_TX_IP_CKSUM      0x1000 /**< IP cksum of TX pkt. computed by NIC. */
>  #define PKT_TX_IPV4_CSUM     0x1000 /**< Alias of PKT_TX_IP_CKSUM. */

These flag values overlap with ones already defined for RX. We have an 
addition 48 flags (47 after you subtract one I reused for control mbuf flag) 
following the mbuf rework, so overlap should not be needed, I think.

/Bruce

  reply	other threads:[~2014-09-29 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  2:02 [dpdk-dev] [PATCH v4 0/8]Support VxLAN on Fortville Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 1/8]i40e:support VxLAN packet identification in librte_ether Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 2/8]i40e:support VxLAN packet identification in librte_pmd_i40e Jijiang Liu
2014-09-29 10:48   ` Bruce Richardson
2014-10-08  3:44     ` Liu, Jijiang
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 3/8]app/test-pmd:test VxLAN packet identification Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 4/8]librte_ether:add a common filter API Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 5/8]i40e:implement API of VxLAN packet filter in librte_pmd_i40e Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 6/8]app/testpmd:test VxLAN packet filter API Jijiang Liu
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 7/8]i40e:support VxLAN Tx checksum offload Jijiang Liu
2014-09-29 10:50   ` Bruce Richardson [this message]
2014-09-26  2:02 ` [dpdk-dev] [PATCH v4 8/8]app/testpmd:test " Jijiang Liu

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=20140929105055.GE12072@BRICHA3-MOBL \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jijiang.liu@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).