DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>, dev@dpdk.org
Cc: linuxarm@huawei.com, xavier_huwei@163.com, xavier.huwei@tom.com,
	forest.zhouchang@huawei.com
Subject: Re: [dpdk-dev] [PATCH] doc: remove Flow Director feature from hns3.ini and hns3_vf.ini
Date: Tue, 15 Oct 2019 12:11:41 +0100	[thread overview]
Message-ID: <19c1a63d-76bd-df62-b86e-901a992f1674@intel.com> (raw)
In-Reply-To: <1570760993-32369-1-git-send-email-xavier.huwei@huawei.com>

On 10/11/2019 3:29 AM, Wei Hu (Xavier) wrote:
> This patch removes deprecated feature 'Flow Director' from hns3.ini
> and hns3_vf.ini because the feature has been removed from the
> feature list in the following commit:
> Commit 030febb6642c ("doc: remove deprecated ethdev features")
> 
> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
> Signed-off-by: Chunsong Feng <fengchunsong@huawei.com>
> ---
>  doc/guides/nics/features/hns3.ini    | 1 -
>  doc/guides/nics/features/hns3_vf.ini | 1 -
>  2 files changed, 2 deletions(-)
> 
> diff --git a/doc/guides/nics/features/hns3.ini b/doc/guides/nics/features/hns3.ini
> index 308048c..6df789e 100644
> --- a/doc/guides/nics/features/hns3.ini
> +++ b/doc/guides/nics/features/hns3.ini
> @@ -16,7 +16,6 @@ RSS key update       = Y
>  RSS reta update      = Y
>  DCB                  = Y
>  VLAN filter          = Y
> -Flow director        = Y
>  Flow control         = Y
>  Flow API             = Y
>  CRC offload          = Y
> diff --git a/doc/guides/nics/features/hns3_vf.ini b/doc/guides/nics/features/hns3_vf.ini
> index a152ca5..41497c4 100644
> --- a/doc/guides/nics/features/hns3_vf.ini
> +++ b/doc/guides/nics/features/hns3_vf.ini
> @@ -13,7 +13,6 @@ RSS hash             = Y
>  RSS key update       = Y
>  RSS reta update      = Y
>  VLAN filter          = Y
> -Flow director        = Y
>  Flow API             = Y
>  CRC offload          = Y
>  VLAN offload         = Y
> 

Indeed I am for adding that feature back to list, sent a mail for it:
https://mails.dpdk.org/archives/dev/2019-October/147203.html

Will proceed with this patch based on its result.

  reply	other threads:[~2019-10-15 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  2:29 Wei Hu (Xavier)
2019-10-15 11:11 ` Ferruh Yigit [this message]
2019-10-25 11:08   ` Thomas Monjalon
2019-10-31 19:04     ` 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=19c1a63d-76bd-df62-b86e-901a992f1674@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=forest.zhouchang@huawei.com \
    --cc=linuxarm@huawei.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xavier.huwei@tom.com \
    --cc=xavier_huwei@163.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).