From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>, bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/enic: add support for TSO
Date: Mon, 9 Jan 2017 11:10:04 +0000 [thread overview]
Message-ID: <93fdc344-8c32-aaad-817a-c33c89aa821c@intel.com> (raw)
In-Reply-To: <20170107044507.2407-1-johndale@cisco.com>
Hi John,
On 1/7/2017 4:45 AM, John Daley wrote:
> The enic TSO implementation requires that the length of the Eth/IP/TCP
> headers be passed to the NIC. Other than that, it's just a matter of
> setting the mss and offload mode on a per packet basis.
>
> In TSO mode, IP and TCP checksums are offloaded even if not requested
> with mb->ol_flags.
>
> Signed-off-by: John Daley <johndale@cisco.com>
Can you please update doc/guides/nics/features/enic.ini to document the
TSO feature in this patch?
Thanks,
ferruh
> ---
<...>
next prev parent reply other threads:[~2017-01-09 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 4:45 John Daley
2017-01-09 11:10 ` Ferruh Yigit [this message]
2017-01-09 18:58 ` [dpdk-dev] [PATCH v2] " John Daley
2017-01-09 23:04 ` [dpdk-dev] [PATCH v3] " John Daley
2017-01-10 10:35 ` Ferruh Yigit
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=93fdc344-8c32-aaad-817a-c33c89aa821c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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).