From: "lipeng (Y)" <lipeng321@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
<davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <salil.mehta@huawei.com>
Subject: Re: [PATCH net-next 17/17] net: hns3: change TM sched mode to TC-based mode when SRIOV enabled
Date: Tue, 19 Dec 2017 09:41:22 +0800 [thread overview]
Message-ID: <3303ceca-5d74-3d15-86e1-f361aaba26ff@huawei.com> (raw)
In-Reply-To: <378b5b7e-e1fc-4c35-d198-8cd9c61b0db9@cogentembedded.com>
On 2017/12/18 17:08, Sergei Shtylyov wrote:
> On 12/18/2017 12:31 PM, Lipeng wrote:
>
>> TC-based sched mode supports SRIOV enabled and SRIOV disabled. This
>> patch change the TM sched mode to TC-based mode in initialization
>> process.
>>
>> Fixes: cc9bb43 (net: hns3: Add tc-based TM support for sriov enabled
>> port)
>
> Need at least 12 hex digits.
>
agree , may lost some hex digits, will fix it.
>> Signed-off-by: Lipeng <lipeng321@huawei.com>
> [...]
>
> MBR, Sergei
>
>
prev parent reply other threads:[~2017-12-19 1:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:31 [PATCH net-next 00/17] add some features and fix some bugs for HNS3 driver Lipeng
2017-12-18 9:31 ` [PATCH net-next 01/17] net: hns3: add support to query tqps number Lipeng
2017-12-18 9:31 ` [PATCH net-next 02/17] net: hns3: add support to modify " Lipeng
2017-12-18 9:31 ` [PATCH net-next 03/17] net: hns3: change the returned tqp number by ethtool -x Lipeng
2017-12-18 9:31 ` [PATCH net-next 04/17] net: hns3: Free the ring_data structrue when change tqps Lipeng
2017-12-18 9:31 ` [PATCH net-next 05/17] net: hns3: Get rss_size_max from configuration but not hardcode Lipeng
2017-12-18 9:31 ` [PATCH net-next 06/17] net: hns3: Add a mask initialization for mac_vlan table Lipeng
2017-12-18 9:31 ` [PATCH net-next 07/17] net: hns3: Add vlan offload config command Lipeng
2017-12-18 9:31 ` [PATCH net-next 08/17] net: hns3: Add ethtool related offload command Lipeng
2017-12-18 9:31 ` [PATCH net-next 09/17] net: hns3: Add handling vlan tag offload in bd Lipeng
2017-12-18 9:31 ` [PATCH net-next 10/17] net: hns3: cleanup mac auto-negotiation state query Lipeng
2017-12-18 9:31 ` [PATCH net-next 11/17] net: hns3: fix for getting auto-negotiation state in hclge_get_autoneg Lipeng
2017-12-18 9:31 ` [PATCH net-next 12/17] net: hns3: add support for set_pauseparam Lipeng
2017-12-18 9:31 ` [PATCH net-next 13/17] net: hns3: add support to update flow control settings after autoneg Lipeng
2017-12-18 9:31 ` [PATCH net-next 14/17] net: hns3: add Asym Pause support to phy default features Lipeng
2017-12-18 9:07 ` Sergei Shtylyov
2017-12-19 1:40 ` lipeng (Y)
2017-12-18 9:31 ` [PATCH net-next 15/17] net: hns3: add support for querying advertised pause frame by ethtool ethx Lipeng
2017-12-18 9:31 ` [PATCH net-next 16/17] net: hns3: Increase the default depth of bucket for TM shaper Lipeng
2017-12-18 9:31 ` [PATCH net-next 17/17] net: hns3: change TM sched mode to TC-based mode when SRIOV enabled Lipeng
2017-12-18 9:08 ` Sergei Shtylyov
2017-12-19 1:41 ` lipeng (Y) [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=3303ceca-5d74-3d15-86e1-f361aaba26ff@huawei.com \
--to=lipeng321@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=sergei.shtylyov@cogentembedded.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