From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id D4B4E47CD for ; Mon, 18 Jul 2016 15:20:28 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id o80so116554042wme.1 for ; Mon, 18 Jul 2016 06:20:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=PSigDOJUQf56EQeP16w00Wndbtg+O7fj0rNqdCjfQNk=; b=FYSe6qzif8PxdeUDEzJ/NNrJkEr1/pyGGiCcyGnIeFW8w2XVRNIO6BopYkGpaJKRQa cpcM23Q49VlkMKdg+VW23MffdW/8GeYdHxs7huTqmfU2cRZXwY8V5XyYuCDBTfVM0iE3 6lW6l0L7LMGy5MgYbbYQKSl3IIhrLECLt64GyhWoqSsL7z92NJFVQHz2fAJwcjEE3+iw z2VpcZGO9M7/hfkFmuZoUPajsKe2mWFIYqLRQMyht4RuozK+QmW3BHPbSvyqbfRZj689 htXv7cW+6qKp1GrSLm1Nwu+w3wuptzzgXeqZarnLHt8aJD6rnqRSS1SivkdpHKj6Dm3W M2fQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=PSigDOJUQf56EQeP16w00Wndbtg+O7fj0rNqdCjfQNk=; b=Apv3z5ijat3T0FF7gr49RD9NH0ZeuQ6fZX0AxyjnnEAZrsoTX8V8aLaNAFtGDdH3kq SWnSci/gm6zjkHtMfwFJxGGT2JjDfebEtwVwqwk8r4xgblxjshDGRexcO8OoBJgLyYZP DyThAul7V5oir+5x7d8KylUMb49mLUh/xHf/ubjTZaCOXMBNhak6ij/G7ll1dZXXrP0z EijvqKqQDFSV1YNHf7ifkQp8K/gY2jKUZrs7LhqyTuAvgYqbxTWW+jDQlVJO9pCjny1v jPUitiWzH233ED80FzeV1T/VJcC3h1QydP0DuxH2MBzLqNgz8R/jMn99VBzM3htjlU70 /cLA== X-Gm-Message-State: ALyK8tLmHpBrd5P7KTGHReEJemK16I3a0ZQbn2U8RLVnM/Ut0n1cPkcCvJoGUuU42pT2Uubo X-Received: by 10.194.17.105 with SMTP id n9mr1197301wjd.121.1468848027969; Mon, 18 Jul 2016 06:20:27 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id n9sm1271620wjk.9.2016.07.18.06.20.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jul 2016 06:20:26 -0700 (PDT) From: Thomas Monjalon To: Sergio Gonzalez Monroy , Akhil Goyal Cc: dev@dpdk.org Date: Mon, 18 Jul 2016 15:20:26 +0200 Message-ID: <3199592.SCxHWQF8fy@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <61dc3eb1-2522-78f5-871d-442d473ab69d@intel.com> References: <61dc3eb1-2522-78f5-871d-442d473ab69d@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] ip_chksum not updated in ipsec-secgw application 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: Mon, 18 Jul 2016 13:20:29 -0000 2016-07-18 13:57, Sergio Gonzalez Monroy: > On 18/07/2016 13:41, Akhil Goyal wrote: > > In Ipsec-secgw application, while adding the outer IP header, > > it seems that the application does not update the checksum value > > for outbound packets. This result in incorrect ip->checksum in > > the encrypted packet. [...] > > It is intentional. The application is using IP checksum offload The correct behaviour is to have a software fallback (using rte_ip.h) for drivers which do not support checksum offload. But given it is just an example, it is normal to have this kind of constraint. However I think it should be explained in its doc. And a list of tested NICs would be nice to have.