From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by dpdk.org (Postfix) with ESMTP id C57452965; Sat, 20 Oct 2018 07:23:07 +0200 (CEST) Received: by mail-wr1-f65.google.com with SMTP id q7-v6so11579606wrr.8; Fri, 19 Oct 2018 22:23:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kEulja9STVZUfF/UiaSlTNGe85+2YTwHc9wsVdDhknw=; b=uBRHxRwol1lNXaCZL477EX4382DdftfFtEI3J+0jIQXYNIBWFOoM0FSDpV9MicERhY UCqEbj9XvHfZ6W8V1ynXZmUWsfstxwjmLbaZpm9L9aLdhhIOSce3B29jC/kzInuhI7XY ae0q5qE7or6+omQDahSa41jK4nBGxiqUB/NoUAxpOGynUMKappITU257cbtwB6U5eFWN yTbg4UFO/Rv+8oDqYktcng0vKvnM1voHhyHZ0SaHLRj9Xtg8ezAyKg0xRZdhWY6wUg+1 h3ChI9M3aXhwSJsNvAZStDj+RgfX+HUPxAtYByj6Q0Y60lnNeBSnhfdtk5BGyyhaOk6J 0WQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kEulja9STVZUfF/UiaSlTNGe85+2YTwHc9wsVdDhknw=; b=NegqXxdHRW0RyRqbZiEFf05rkIYc7QuvoOxi27wQLgxSRz7RCGWJ1GLBqrmcsEXgMz bfIwNDVbaQjovXKAUaRahLNx9oe1SbPOTvIbziHLXz8QGrIvmvap7VzPU8XSiqRKfNhP wUBvqq3oEkeEFhJmA1agRAqsrRYUGJBKjBipy9s+bLHzIgn4mWIXML7rHSMq8AWs1MAe JoGTVUWI10BYpYXFAoe8vn+nSfopPjDjuxvr8RxlmGBLfmkyXyNHkCUgo0JBaAtvY0Gc pPhfYy/LX20u5mtzDLjPncEfnsURkgIIbNz9otkTqbjHNQIx6BNhkacPlvAXpiGPvv85 K+hw== X-Gm-Message-State: AGRZ1gKpUbHx9mIL3DIWy1siSmcoOrRizvvafmNLPw0OuEO2Vui8h931 2HsnIfg6zH0HgUpBGWt9ITUCXdGc+L2XxLClXf4= X-Google-Smtp-Source: AJdET5e6vBwYkZEGrgbT+NUKBmyZh6ILibBoY71LtrkXAwbL3mWg12KGzXH6eNQPsEJC8gWDFtbf9p9HvP2TpE2+aS8= X-Received: by 2002:adf:dcc4:: with SMTP id x4-v6mr606435wrm.212.1540012987273; Fri, 19 Oct 2018 22:23:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Shyam Shrivastav Date: Sat, 20 Oct 2018 10:52:50 +0530 Message-ID: To: lidejun1@huawei.com Cc: users , dev@dpdk.org, lichunhe@huawei.com, wangliefeng@huawei.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] IPV4/IPV6 TCP/UDP Pseudo Header Checksum APIs 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: Sat, 20 Oct 2018 05:23:07 -0000 Realized my answer is confusing, I meant to say that code is correct as pseudo ipv4/ipv6 headers for the purpose of checksum calculations doesn't include options or extension headers, see udp wiki or corresponding rfcs https://en.wikipedia.org/wiki/User_Datagram_Protocol On Sat, Oct 20, 2018 at 10:42 AM Shyam Shrivastav < shrivastav.shyam@gmail.com> wrote: > that is correct , pseudo header doesn't include ipv4 options or ipv6 > extension headers .. > > On Sat, Oct 20, 2018 at 9:02 AM lidejun wrote: > >> Has anybody used the following two APIs calculating ipv4&ipv6 tcp/udp >> pseudo header checksum=EF=BC=9F >> >> 1. rte_ipv4_phdr_cksum >> >> 2. rte_ipv6_phdr_cksum >> The ipv4 version does not exclude ip options and ipv6 version does not >> exclude extersion headers. >> >