From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: miroslaw.walukiewicz@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/3] pmd: add new header containing TCP offload specific definitions
Date: Tue, 14 Oct 2014 11:50:22 +0200 [thread overview]
Message-ID: <1661299.7FS05kkgmX@xps13> (raw)
In-Reply-To: <20141013143840.19211.79771.stgit@gklab-18-011.igk.intel.com>
Hi Miroslaw,
2014-10-13 10:38, miroslaw.walukiewicz@intel.com:
> From: Miroslaw Walukiewicz <miroslaw.walukiewicz@intel.com>
>
> The function for computing initial TCP header checksum.
> The file is common for both i40e and ixgbe PMD drivers
>
> Signed-off-by: Mirek Walukiewicz <miroslaw.walukiewicz@intel.com>
> ---
> lib/librte_net/Makefile | 3 +
> lib/librte_net/rte_tcp_off.h | 122 ++++++++++++++++++++++++++++++++++++++++++
There is a work in progress about TSO:
http://thread.gmane.org/gmane.comp.networking.dpdk.devel/2541/focus=2553
This API was discussed and implemented for ixgbe.
Then there was an agreement to rework mbuf in 1.8 version to implement TSO
on top of it. Then it was suggested to rebase his work:
http://dpdk.org/ml/archives/dev/2014-September/006151.html
How does your patchset match with Olivier's work on TSO and ixgbe driver?
I would like to ensure the API works fine for all TSO-capable driver,
this would be a good start.
Thanks
--
Thomas
next prev parent reply other threads:[~2014-10-14 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 14:38 [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation on the packet miroslaw.walukiewicz
2014-10-13 14:38 ` [dpdk-dev] [PATCH 2/3] pmd: add new header containing TCP offload specific definitions miroslaw.walukiewicz
2014-10-14 9:50 ` Thomas Monjalon [this message]
2014-10-13 14:38 ` [dpdk-dev] [PATCH 3/3] pmd i40e: Enable Transmit Segmentation Offload for TCP traffic miroslaw.walukiewicz
2014-10-14 7:47 ` [dpdk-dev] [PATCH 1/3] pmd: add new flag to indicate TX TSO operation on the packet Liu, Jijiang
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=1661299.7FS05kkgmX@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=miroslaw.walukiewicz@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).