test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Lijuan Tu <lijuanx.a.tu@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH v1 0/3] Change "tx-offloads" configuration
Date: Fri, 26 Jan 2018 00:14:00 +0800	[thread overview]
Message-ID: <5A6A0248.4020503@intel.com> (raw)
In-Reply-To: <1516894993-29702-1-git-send-email-lijuanx.a.tu@intel.com>

Thanks, Lijuan. Applied.

On 01/25/2018 11:43 PM, Lijuan Tu wrote:
> Current framework will enable all offloads ,but in some NIC don't support
> all of them. Remove this setting from framework , and handle it in case
> script.
>
> In our NICs ,jumboframe need enable multi segment send

      parent reply	other threads:[~2018-01-25  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:43 Lijuan Tu
2018-01-25 15:43 ` [dts] [PATCH v1 1/3] framework: Remove option "tx--offloads" Lijuan Tu
2018-01-25 15:43 ` [dts] [PATCH v1 2/3] tests: reset "tx-offloads" to defualt Lijuan Tu
2018-01-25 15:43 ` [dts] [PATCH v1 3/3] jumboframe & vf_jumboframe: set tx offloads Lijuan Tu
2018-01-25 16:14 ` Liu, Yong [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=5A6A0248.4020503@intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuanx.a.tu@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).