DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] support TSO on i40e
Date: Fri, 13 Feb 2015 01:32:58 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8BA72E8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1423463570-12947-1-git-send-email-jijiang.liu@intel.com>

Hi, Jijiang

I guess you may miss the "V2" in the title?

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jijiang Liu
> Sent: Monday, February 09, 2015 2:33 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/2] support TSO on i40e
> 
> This patch set enables i40e TSO feature for both non-tunneling packet and
> tunneling packet.
> 
> Change logs:
>     v2 change: rework based on Olivier's patch set [PATCH v2 00/20] enhance
> tx checksum offload API
> 		http://dpdk.org/ml/archives/dev/2015-
> February/012375.html
> 
> Jijiang Liu (2):
>   advertise TSO capability in the i40e PMD
>   enable i40e TSO feature
> 
>  lib/librte_pmd_i40e/i40e_ethdev.c |    3 +-
>  lib/librte_pmd_i40e/i40e_rxtx.c   |   99 +++++++++++++++++++++++++++---
> -------
>  lib/librte_pmd_i40e/i40e_rxtx.h   |   13 +++++
>  3 files changed, 87 insertions(+), 28 deletions(-)
> 
> --
> 1.7.7.6

  parent reply	other threads:[~2015-02-13  1:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09  6:32 Jijiang Liu
2015-02-09  6:32 ` [dpdk-dev] [PATCH 1/2] i40e:advertise TSO capability Jijiang Liu
2015-02-09  9:09   ` David Marchand
2015-02-09  6:32 ` [dpdk-dev] [PATCH 2/2] i40e:enable TSO support Jijiang Liu
2015-02-09  9:10   ` David Marchand
2015-02-20 15:54     ` Walukiewicz, Miroslaw
2015-02-13  1:32 ` Wu, Jingjing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-16  2:31 [dpdk-dev] [PATCH 0/2] support TSO on i40e Jijiang Liu
2015-01-16 16:44 ` Ananyev, Konstantin

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=9BB6961774997848B5B42BEC655768F8BA72E8@SHSMSX104.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jijiang.liu@intel.com \
    /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).