From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 43CF37F40 for ; Thu, 20 Nov 2014 17:25:56 +0100 (CET) Received: by mail-wg0-f43.google.com with SMTP id l18so4188068wgh.30 for ; Thu, 20 Nov 2014 08:36:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Rx8uQdLEVAXgPr+8A9F+r6qkoMOBUXufRHLIdGHVJOc=; b=EW8OKNX8h59ARYZOalh6PL4M5aTuAYPuixdN3QjfN0tlDrmXgkmlPNV1yI/4kAdn6U Z5iV/CtiMVTq531q4ndXDCN+TXQKiwwqvnMNhJXJXTCRfuFt80HpxQnsnUuSvEXP8ylh +GRt5+t5hWxynUh4uGQ0g70o8cW0y52cUmGjyXqweaLBCdgBbskC8uGZGfm4WiC6Ok2L FnDfSMy1gWyKQoAIdh6T7Dw46LDXJSmQISxQk/Wj9c+Qi8xL+uFN+AJjkPay2V/dWMI/ jfCNfpCW4X1m5104AmL0pNEvhJ19FTxlSKemnx98jOJsawylfXDoJbfBccWDMbm99FHU 9gQA== X-Gm-Message-State: ALoCoQm9MvzsZH0Oaz0zxBYcfuN7jidQc3ga7I3SvH0PzdyadSWCavfcl9IYyzVCOFk8yoiAoSEa X-Received: by 10.194.92.148 with SMTP id cm20mr71165963wjb.88.1416501384863; Thu, 20 Nov 2014 08:36:24 -0800 (PST) Received: from [10.16.0.195] (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by mx.google.com with ESMTPSA id vm8sm4101626wjc.6.2014.11.20.08.36.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Nov 2014 08:36:24 -0800 (PST) Message-ID: <546E1887.1020800@6wind.com> Date: Thu, 20 Nov 2014 17:36:23 +0100 From: Olivier MATZ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 MIME-Version: 1.0 To: "Liu, Jijiang" References: <1414376006-31402-1-git-send-email-jijiang.liu@intel.com> <176980123.CbUgamS8oi@xps13> <1ED644BD7E0A5F4091CF203DAFB8E4CC01D992F8@SHSMSX101.ccr.corp.intel.com> <3175184.TxKMqZeb6U@xps13> <1ED644BD7E0A5F4091CF203DAFB8E4CC01D9B646@SHSMSX101.ccr.corp.intel.com> <5465C6DD.4000000@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01D9BAC0@SHSMSX101.ccr.corp.intel.com> <5469DA40.7050107@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01D9C383@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D9C383@SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev Subject: Re: [dpdk-dev] [PATCH v8 10/10] app/testpmd:test VxLAN Tx checksum offload X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2014 16:25:57 -0000 Hi Jijiang, On 11/20/2014 08:28 AM, Liu, Jijiang wrote: >> The original behavior (without your vxlan patches), which still works today, is to >> select inner or outer using the m->l2_len field: >> >> - checksum outer IP + UDP >> m->l2_len=14 m->l3_len=20 >> flags=PKT_TX_IP_CKSUM PKT_TX_UDP_CKSUM >> >> - checksum inner IP + UDP >> m->l2_len=64 m->l3_len=20 >> flags=PKT_TX_IP_CKSUM PKT_TX_UDP_CKSUM >> of course, the packet is valid only if the outer IP checksum is >> already correct and outer UDP checksum is 0 >> >> If i40e does not act like this, it does not follow the previous API. > > No, i40e follows this. OK. This is assumption (A): To calculate the inner IP + UDP checksum, you don't need VXLAN flag. You just acked it. >>> 2. only set inner L3/L4 header TX checksum >>> tx_checksum set 0x30 0 >>> In this case, the PKT_TX_VXLAN_CKSUM flag is set, so driver think it is VXLAN >> packet, and we don't need to change outer ones because we don't set outer flags >> here (PKT_TX_IPV4_CSUM, PKT_TX_UDP_CKSUM). Assumption (B): To calculate the inner IP + UDP checksum (this is what you wrote "only set inner L3/L4 header TX checksum"), you say you set the VXLAN flag. This is the opposite of (A). >> As explained above, there is no need to set the PKT_TX_VXLAN_CKSUM if you >> only want to set the inner L3/L4 checksum. >> This was already working like this >> before your patches, as long as l2_len and l3_len are set properly in the mbuf >> (l2_len should include the outer headers). > > Does VXLAN TX checksum offload or ordinary L2 packet TX checksum offload work? > Have you ever tested it on a NIC that supports VXLAN. You don't answer the question: which between (A) or (B) is correct. I'm sorry I don't understand your question above. I have done no test on i40e, because I don't have access to this hardware. > The PKT_TX_VXLAN_CKSUM flag meaning just tell driver this is encapsulation packet, so driver should set TX checksum offload for the packet using outer l2/l3 len, inner l2/l3 len and tunneling header length. > > If you don't like this flag name, I can change it for PKT_TX_TUNNEL_CKSUM, which have more generic meaning. The problem is not only the name. After tens of mails, I'm still not able to understand the VxLAN checksum API. I wanted to rework the csum forward engine code, because it is not understable today. I wanted to clarify the API. But sorry I think I'll give up now. >> Moreover, PKT_TX_IPV4_CSUM, PKT_TX_UDP_CKSUM, ... are not "outer flags". >> They are hardware checksum flags, and before your vxland patch, they concerned >> the headers referenced by m->l2_len and m->l3_len. > > Actually, the key point of debate is that you still think the l2_len filed and the l3_len filed in mbuf are inner part in the case of tunneling, right? If yes, let me explain what I thought. This is not the only key point of debate. The very first key point is that the VxLAN checksum offload API is not documented and I'm not able to rework the csum code to use it. > As you know, NIC itself is not responsible for packet decapsulation / encapsulation at all. It sends and receives the whole packet, not only for inner part in the case of tunneling. The translation from receive descriptor to mbuf structure is also for the whole packet. And these fields defined in mbuf structure are also for the whole packet, no matter it is tunneling or non-tunneling. > > 1) We assume that a NIC can't recognize VXLAN packet, when a packet with the format outer IP / outer UDP / VxLAN / Ether / inner IP / inner UDP / data is received, > do you think whether l2 header and l3 header length of this packet is outer or inner, according to my understanding, I think it is outer, and m->l2_len and m->l3_len is also outer. Do you agree? The l2_len and l3_len are never set up by any driver on rx side. Your example does not apply. These fields are set by the application (a network stack for instance) to indicate to the driver and hardware where to find the l3 and l4 headers whose checksum need to be calculated. The l2_len and l3_len does not refer to inner or outer header. It refers to the header that has to be checksum'd in hardware when the flag is set. It can be inner or outer. At least, it was the case before the adding of VxLAN offload feature. > 2) We also assume that a NIC can recognize VXLAN packet, but there is no difference between 1) and 2) on data in mbuf before patching my VXLAN patch, so I also think m->l2_len and m->l3_len is outer. Do you agree? > After patching my VXLAN, the inner_l2_len and inner_l3_len were used to stand for inner header part. Your argumentation would make sense if l2_len and l3_len were filled by a NIC in RX functions. But that's not the case. Today, these fields are only used in TX when a checksum flag is also set. And I think that a flag should always refer to the same length fields. But I'm not the one who decides this, I'm just trying to help to define an API that makes sense. >> With your vxlan patch, it changed without beeing documented. These flags use >> either (m->l2_len, m->l3_len) or (m->inner_l2_len, >> m->inner_l3_len), which is not a good idea in my opinion. > > The PKT_RX_IPV4_HDR definition is listed below, > #define PKT_RX_IPV4_HDR (1ULL << 5) /**< RX packet with IPv4 header. */ > I don't think it just stand for inner IP TX checksum offload, I just extend its usage scope in the case of tunneling. If you reread my mail, I was not talking about PKT_RX_IPV4_HDR but about PKT_TX_IPV4_CSUM, PKT_TX_UDP_CKSUM, (etc...) which are TX flags. I think my previous mail was clear enough: They are hardware checksum flags, and before your vxlan patch, they concerned the headers referenced by m->l2_len and m->l3_len. With your vxlan patch, it changed without beeing documented. These flags use either (m->l2_len, m->l3_len) or (m->inner_l2_len, m->inner_l3_len), which is not a good idea in my opinion. >>> 3. set outer L3/L4 TX checksum and inner L3&L4 TX checksum tx_checksum >>> set 0x31(0x33) 0 in this case, the PKT_TX_VXLAN_CKSUM flag is set, >>> driver think it is VXLAN packet, and we need to change outer and inner as both >> outer and inner flags are set. >> >> Here you are talking about test pmd flags. You do not describe the mbuf API: >> PKT_TX_* flags and lengths values that need to be set (l2_len, l3_len, ...) and to >> what they refer to. >> >> I think if you want to explain the vxlan checksum offload mbuf API, you should not >> talk about the testpmd flags as: >> - they don't match the mbuf flags >> - they have undocumented (or uncoherent) behavior in the csumonly >> forward engine >> >> After several exchanges about this vxlan API. >> Unfortunately, it is still vague and obscure to me. > > As to tunneling packet TX checksum offload, please don't think it is only an inner or outer part. > You should regard it as whole part. So what? >> So here is a proposition of API documentation that looks understandable. Maybe >> it is easier to change the code to match this API: >> > Ok, thanks. > >> >> PKT_TX_IP_CKSUM flag enables hardware computation of IP cksum. To use it: >> - fill l2_len and l3_len in mbuf >> - set the flag PKT_TX_IP_CKSUM >> - set the ip checksum to 0 in IP header >> See (1) and (2). >> >> One value among PKT_TX_L4_NO_CKSUM, PKT_TX_UDP_CKSUM, >> PKT_TX_TCP_CKSUM and PKT_TX_SCTP_CKSUM can be assigned to the bits of >> PKT_TX_L4_MASK. These flags are used to offload the L4 checksum in hardware. >> The user requires to: >> - fill l2_len and l3_len in mbuf >> - set the flags PKT_TX_TCP_CKSUM, PKT_TX_SCTP_CKSUM or >> PKT_TX_UDP_CKSUM >> - calculate the pseudo header checksum and set it in the L4 >> header (only for TCP or UDP). See rte_ipv4_phdr_cksum() and >> rte_ipv6_phdr_cksum(). For SCTP, set the crc field to 0. >> See (1) and (2). >> >> The PKT_TX_TCP_SEG flag can be set to enable TCP segmentation offload for a >> packet to be transmitted on hardware supporting >> TSO: >> - set the PKT_TX_TCP_SEG flag in mbuf->ol_flags (this flag >> implies PKT_TX_TCP_CKSUM) >> - if it's IPv4, set the PKT_TX_IP_CKSUM flag and write the IP >> checksum to 0 in the packet >> - fill the mbuf offload information: l2_len, l3_len, l4_len, >> tso_segsz >> - calculate the pseudo header checksum without taking ip_len in >> accound, and set it in the TCP header. Refer to >> rte_ipv4_phdr_cksum() and rte_ipv6_phdr_cksum() that can be >> used as helpers. >> See (1) and (2). >> >> (1) In case the packet is an encapsulated packet, the m->l2_len >> field can include all the outer tunnel headers. These headers >> will remain unmodified by the hardware. >> >> (2) If outer_l2_len and outer_l3_len are not 0, the beginning of >> the inner headers is relative to outer_l2_len + outer_l3_len. >> >> >> [To replace the PKT_TX_VXLAN_CKSUM, we introduce 2 new flags] >> >> PKT_TX_OUTER_IP_CKSUM flag enables hardware computation of IP cksum in >> outer headers. To use it: >> - fill outer_l2_len and outer_l3_len in mbuf >> - set the flag PKT_TX_OUTER_IP_CKSUM >> - set the ip checksum to 0 in outer IP header >> >> One value among PKT_TX_OUTER_L4_NO_CKSUM, >> PKT_TX_OUTER_UDP_CKSUM, PKT_TX_OUTER_TCP_CKSUM and >> PKT_TX_OUTER_SCTP_CKSUM can be assigned to the bits of PKT_TX_L4_MASK. >> These flags are used to offload the outer L4 checksum in hardware. >> The user requires to: >> - fill outer_l2_len and outer_l3_len in mbuf >> - set the flags PKT_TX_OUTER_TCP_CKSUM, PKT_TX_OUTER_SCTP_CKSUM or >> PKT_TX_OUTER_UDP_CKSUM >> - calculate the pseudo header checksum and set it in the outer L4 >> header (only for TCP or UDP). See rte_ipv4_phdr_cksum() and >> rte_ipv6_phdr_cksum(). For SCTP, set the crc field to 0. > > Good. You provide a common approach. > > Actually, I have another common approach, > 1. Change PKT_TX_VXLAN_CKSUM to PKT_TX_TUNNEL_CKSUM > 2. Add field "uint8_t tun_header_len "(tunneling header length, for example, GRE header )into mbuf structure. > After above change, the API can supports other tunnels. No. I don't want that you explain me what should be modified in the current API, as I don't understand it. I need (the community needs?) a full definition of the API, like I just did in my previous mail. I think my description was clear. Please, do the same effort to describe the vxlan API from the beginning to the end, and how it changes (or not) the legacy checksum API. >> This proposition has several advantages: >> - it is documented :) >> - the API is straightforward: inner and outer work in the same >> manner. >> - the API already supports other tunnels (IPIP, GRE, STT, ...) >> - adding m->outer_* fields allows to keep the same semantic for >> the existing flags. Indeed, it does not map linux skb, but this >> is not an argument. Moreover, linux does not seem to support >> hardware tx checksum of outer+inner headers. > > Just as I have mentioned in the previous email, Linux have already supported hardware tx checksum of outer+inner headers for i40e. Yes you are right. But I think that's not the point here. Regards, Olivier