From: David Miller <davem@davemloft.net>
To: salil.mehta@huawei.com
Cc: yisen.zhuang@huawei.com, lipeng321@huawei.com,
mehta.salil@opnsrc.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH net-next 0/7] Support of Flow Director in HNS3 Ethernet Driver for HiP08 Rev2 SoC
Date: Mon, 01 Oct 2018 22:58:08 -0700 (PDT) [thread overview]
Message-ID: <20181001.225808.1703753605069754507.davem@davemloft.net> (raw)
In-Reply-To: <20181001114647.15504-1-salil.mehta@huawei.com>
From: Salil Mehta <salil.mehta@huawei.com>
Date: Mon, 1 Oct 2018 12:46:40 +0100
> This patch-set adds the support of FD(Flow Director) in the HNS3 PF driver
> for HiP08 Rev2(0x21) SoC of Hisilicon. FD can be used in filtering the flows
> and deciding to drop the flow or forward it to paricular queue.
>
> Configuration consists of rules with input keys and actions. The rules are
> stored in TCAM.
Series applied.
prev parent reply other threads:[~2018-10-02 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 11:46 [PATCH net-next 0/7] Support of Flow Director in HNS3 Ethernet Driver for HiP08 Rev2 SoC Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 1/7] net: hns3: Add flow director initialization Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 2/7] net: hns3: Add input key and action config support for flow director Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 3/7] net: hns3: Add support for rule add/delete " Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 4/7] net: hns3: Add support for rule query of " Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 5/7] net: hns3: Add reset handle for " Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 6/7] net: hns3: Remove all flow director rules when unload hns3 driver Salil Mehta
2018-10-01 11:46 ` [PATCH net-next 7/7] net: hns3: Add support for enable/disable flow director Salil Mehta
2018-10-02 5:58 ` David Miller [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=20181001.225808.1703753605069754507.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=mehta.salil@opnsrc.net \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@huawei.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