From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f180.google.com (mail-pf0-f180.google.com [209.85.192.180]) by dpdk.org (Postfix) with ESMTP id AA4081B3B6 for ; Sun, 17 Jun 2018 18:46:34 +0200 (CEST) Received: by mail-pf0-f180.google.com with SMTP id q1-v6so7012830pff.13 for ; Sun, 17 Jun 2018 09:46:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=CFIszih1+EIKjv8s2erXuB5s1VDrT1SgQKdZw+fqjN8=; b=eiZnq795ojsSw3EHa7Q9NZnHmqlugKfTxWoE3Wh5feS/MaONeQePPzzcIxCI1ig1W7 u6GDqlMD8ijVM+r0U9FfvLErPmIi9A81dK6sev85nmkHG5pjwB36cNzaA1V/+Mcy7DQA GgBcfly29/A+fQmjB5mO2Q4hEsvvO3YWrWdsJnWEG3zcoi3HACKfxpL3dIJue7ttI8bo hJEZocF+C/McrIoaFMFJVD450fjUPs2xiRxM8/fLlaQ6ivbe/ihNM2he0LPIvrhb479S g27vHGkdPzBJS61i/9YV3wg7n6PMaA0leOIXoyghkaXf/so1SmSLX/Rug7fu11lp5hys qLeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=CFIszih1+EIKjv8s2erXuB5s1VDrT1SgQKdZw+fqjN8=; b=SP7aUHvVpAyjDoDj3ojOgslapyXeE0E9/3/0YlbRyVpRz7enzazWqRxG9a6smWqhX8 PqmhF0hoh2mRkS3M94STNwcmq1AbJy6HdD1Db/4V0wdYK5HMr43UF1Tu1biQNEsVLoCs hd4gEvdQ8jGJe7EHwRZAdjSaTjh3coAMx7nV+mtTrnD9Kgahf2QFHBcq2iG5hurjWTL9 qTmdXFkcTWtp/y2C/Ohn0vxPWj3UumJUuRTcacbraCp4hnnR3b2wP7yrTwHzQHAtipkk m3AkAXDWBD2br9Pwz6fZIfHWFSsZVieFnAKbIDMtjAqrCOumbZ0kEk3nW6RYPw3X/oBU o4bQ== X-Gm-Message-State: APt69E0ZzZi/Mtf3k53Wm2ihJtW2Vt79klPIOyBDSzJa5y9boWIszKSS R5yUw3tr/VYGBL8B4slUSA4l9KwOtZQ= X-Google-Smtp-Source: ADUXVKLZhBTVnsVFg7LZFNuKeLGJ3zmYhII57nz2HXx2C6oYs1UrJCHph4G3bkfLKmuxEyXrGTrqOA== X-Received: by 2002:a62:808f:: with SMTP id j137-v6mr10269430pfd.91.1529253993720; Sun, 17 Jun 2018 09:46:33 -0700 (PDT) Received: from xeon-e3 (204-195-35-107.wavecable.com. [204.195.35.107]) by smtp.gmail.com with ESMTPSA id t23-v6sm24564839pfa.86.2018.06.17.09.46.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 17 Jun 2018 09:46:33 -0700 (PDT) Date: Sun, 17 Jun 2018 09:46:26 -0700 From: Stephen Hemminger To: Padam Jeet Singh Cc: dev@dpdk.org, yongwang@vmware.com Message-ID: <20180617094626.2d72413f@xeon-e3> In-Reply-To: <45FFB08E-61C4-456F-A332-0881B6BF2BE3@inventum.net> References: <45FFB08E-61C4-456F-A332-0881B6BF2BE3@inventum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] vmxnet3 TX TCP/UDP checksum not getting computed with L2_len > 14 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 16:46:34 -0000 On Sun, 17 Jun 2018 14:55:06 +0530 Padam Jeet Singh wrote: > Hello, >=20 > Issue observed when using vmxnet3 based interface on packet with followin= g structure is sent: >=20 > Ethernet + PPPoE + PPP (22 bytes) as the Layer 2 header,=20 > IPv4 (20)=20 > UDP > DNS Payload >=20 > The tx offload value in this case is 0x0f0000000000000 (PKT_TX_IPV4 | PK= T_TX_IP_CKSUM | PKT_TX_UDP_CKSUM) >=20 > The checksum of the packet seen by the receiver shows incorrect checksum = and it=E2=80=99s value is the pseudo checksum value that was set at the tim= e of the TX. However the IP header checksum is correct. >=20 > The same issue is not seen when the L2 header is a just the Ethernet (14 = bytes). >=20 > Also, with the same setup on the same hardware if we switch the driver fr= om vmxnet3 to e1000e, all checksums are computed correctly. >=20 > Is this a DPDK vmxnet3 driver bug or that of underlying esxi? The ESXi ve= rsion is 6.0.0 (Build 3620759). >=20 > Thanks, > Padam I don't think VMWare supports IP checksum offload. Since IP checksum is tri= vial and in cache, the IP header checksum offload is usually not a speed up anyway. Linux for = example, never does IP header checksum offload.