DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jiayu Hu <jiayu.hu@intel.com>, dev@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v5] app/testpmd: enable the heavyweight mode TCP/IPv4 GRO
Date: Sat, 7 Oct 2017 08:58:37 +0100	[thread overview]
Message-ID: <d6f2e43d-3a85-cd50-5fb9-2b62823cda4d@intel.com> (raw)
In-Reply-To: <1507362357-30352-1-git-send-email-jiayu.hu@intel.com>

On 10/7/2017 8:45 AM, Jiayu Hu wrote:
> The GRO library provides two modes to reassemble packets. Currently, the
> csum forwarding engine has supported to use the lightweight mode to
> reassemble TCP/IPv4 packets. This patch introduces the heavyweight mode
> for TCP/IPv4 GRO in the csum forwarding engine.
> 
> With the command "set port <port_id> gro on|off", users can enable
> TCP/IPv4 GRO for a given port. With the command "set gro flush <cycles>",
> users can determine when the GROed TCP/IPv4 packets are flushed from
> reassembly tables. With the command "show port <port_id> gro", users can
> display GRO configuration.
> 
> The GRO library doesn't re-calculate checksums for merged packets. If
> users want the merged packets to have correct IP and TCP checksums,
> please select HW IP checksum calculation and HW TCP checksum calculation
> for the port which the merged packets are transmitted to.
> 
> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Tested-by: Yao Lei <lei.a.yao@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-10-07  7:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10  2:50 [dpdk-dev] [PATCH 0/2] Support the Heavyweight Mode GRO in Testpmd Jiayu Hu
2017-08-10  2:50 ` [dpdk-dev] [PATCH 1/2] app/testpmd: support the heavywight mode GRO Jiayu Hu
2017-08-10  9:50   ` Ferruh Yigit
2017-08-15  6:01     ` Jiayu Hu
2017-08-10  2:50 ` [dpdk-dev] [PATCH 2/2] doc: update testpmd user guide for the heavyweight " Jiayu Hu
2017-08-17  9:08 ` [dpdk-dev] [PATCH v2 0/2] Support the Heavyweight Mode GRO in Testpmd Jiayu Hu
2017-08-17  9:08   ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: support the heavywight mode GRO Jiayu Hu
2017-08-21 11:03     ` Ferruh Yigit
2017-08-22  1:00       ` Hu, Jiayu
     [not found]         ` <671112a6-6ac6-7476-4270-be1a0258f06e@intel.com>
2017-08-22 14:27           ` Jiayu Hu
2017-08-21 11:16     ` Ferruh Yigit
2017-08-22  0:53       ` Hu, Jiayu
2017-08-17  9:08   ` [dpdk-dev] [PATCH v2 2/2] doc: update testpmd user guide for the heavyweight " Jiayu Hu
2017-08-21 11:03     ` Ferruh Yigit
2017-08-22  0:52       ` Hu, Jiayu
2017-09-03  6:30   ` [dpdk-dev] [PATCH v3] app/testpmd: enable the heavyweight mode TCP/IPv4 GRO Jiayu Hu
2017-09-20  7:00     ` Yao, Lei A
2017-09-25 10:20       ` Hu, Jiayu
2017-09-26  3:54         ` Hu, Jiayu
2017-09-25 11:11     ` Ferruh Yigit
2017-09-26  6:26     ` [dpdk-dev] [PATCH v4] " Jiayu Hu
2017-09-27  7:23       ` Yao, Lei A
2017-10-06 23:04         ` Ferruh Yigit
2017-10-06 23:26           ` Ferruh Yigit
2017-10-07  0:51             ` Hu, Jiayu
2017-10-07  7:45       ` [dpdk-dev] [PATCH v5] " Jiayu Hu
2017-10-07  7:58         ` Ferruh Yigit [this message]

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=d6f2e43d-3a85-cd50-5fb9-2b62823cda4d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=thomas@monjalon.net \
    /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).