From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Michael Qiu <qdy220091330@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Michael Qiu <qiudayu@chinac.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] examples/tep_term: Fix l4_len issue
Date: Mon, 24 Oct 2016 05:41:24 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E364E6C3573@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1476769747-23289-1-git-send-email-qiudayu@chinac.com>
> -----Original Message-----
> From: Michael Qiu [mailto:qdy220091330@gmail.com]
> Sent: Tuesday, October 18, 2016 1:49 PM
> To: dev@dpdk.org
> Cc: Tan, Jianfeng; Michael Qiu
> Subject: [PATCH 1/2] examples/tep_term: Fix l4_len issue
>
> l4_len is not fixed, althrough mostly it is a fixed value,
> but when guest using iperf to do some tests, the l4_len
> will have another 12 bytes optional fields.
>
> Fixes: 2bb43bd4350a("examples/tep_term: add TSO offload configuration")
>
> Signed-off-by: Michael Qiu <qiudayu@chinac.com>
Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
Thanks,
Jianfeng
prev parent reply other threads:[~2016-10-24 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 5:49 Michael Qiu
2016-10-18 5:49 ` [dpdk-dev] [PATCH 2/2] examples/tep_term: Fix packet len for multi-seg mbuf Michael Qiu
2016-10-24 5:41 ` Tan, Jianfeng
2016-10-25 15:53 ` Thomas Monjalon
2016-10-24 5:41 ` Tan, Jianfeng [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=ED26CBA2FAD1BF48A8719AEF02201E364E6C3573@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=qdy220091330@gmail.com \
--cc=qiudayu@chinac.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).