DPDK usage discussions
 help / color / mirror / Atom feed
From: topperxin <topperxin@126.com>
To: users@dpdk.org
Subject: [dpdk-users] how to calculate the checksum for tcp segment from gso output
Date: Mon, 27 Nov 2017 16:23:10 +0800 (CST)	[thread overview]
Message-ID: <52738422.b154.15ffc92a890.Coremail.topperxin@126.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 720 bytes --]

HI list

         In the 17.11 version ,lib gso was introduced.
         I just want to check it's performance.
        The output segments from the rte_gso_segments() were multi-segments mbuf, at the same time, rte_gso_segments() don't calculate the checksum for the out put tcp seg, so , the application have to calculate the csum by itself.
        But the current rte_udptcp_csum() interface can't calculate the checksum of multi-segment mbuf.

        Who know how to do it? 
    
\x16º&®‰^¶×¢ø§Š×¢ Ê'6‹öï]÷ëm¶Ó^ÑzÛ«œö­†º%zÛ^Šwâž+^Š„^qè¯y×ë¢išŠ\&Ñþx‚Š •ç(šf¢—	´\x7fž ¢ˆ%yÊ&ïvç͹Ἕ¥Ù(®\x03è²×âÇ\b­„DŒLøÜ=9\x0fPu\x03Wè®ë\x1e®ÇivJ+€Ê'Û³h¿m5ï]÷ëm¾Ó]4\bDÑyÇ¢½ç[Êf¢—	´\x7fž ¢ˆ%yÊ&Â+aHÄωۼÞÊ7ßÞüçŽp™¾_¢»¬z»\x1d¥Ù(®\x03(ŸnÍ¢ý´×½8ß­¶ÓÍ4=$Ã(ƒ\x12Š	Ú¶êÞ

                 reply	other threads:[~2017-11-27  8:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52738422.b154.15ffc92a890.Coremail.topperxin@126.com \
    --to=topperxin@126.com \
    --cc=users@dpdk.org \
    /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).