From: Ferruh Yigit <ferruh.yigit@intel.com>
To: oulijun <oulijun@huawei.com>,
thomas@monjalon.net, arybchenko@solarflare.com
Cc: dev@dpdk.org, linuxarm@openeuler.org
Subject: Re: [dpdk-dev] [PATCH v2 4/5] doc: update release notes for hns3
Date: Fri, 29 Jan 2021 08:48:15 +0000 [thread overview]
Message-ID: <3e5f308c-8dd1-4aa1-b957-05f5e2dca67d@intel.com> (raw)
In-Reply-To: <e2cc6c0d-6a31-d41a-0f98-7b6627e6840f@huawei.com>
On 1/29/2021 1:28 AM, oulijun wrote:
>
>
> 在 2021/1/28 22:46, Ferruh Yigit 写道:
>> On 1/28/2021 12:43 PM, Lijun Ou wrote:
>>> Add TM(Traffic Management) feature with hns3 in release notes.
>>> It includes:
>>> 1. configure port's peak rate with PF
>>> 2. configure TC's peak rate with PF
>>>
>>> Fixes: c09c7847d892 ("net/hns3: support traffic management")
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Lijun Ou <oulijun@huawei.com>
>>> ---
>>> doc/guides/rel_notes/release_21_02.rst | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/doc/guides/rel_notes/release_21_02.rst
>>> b/doc/guides/rel_notes/release_21_02.rst
>>> index 23dcb37..08b73de 100644
>>> --- a/doc/guides/rel_notes/release_21_02.rst
>>> +++ b/doc/guides/rel_notes/release_21_02.rst
>>> @@ -82,6 +82,11 @@ New Features
>>> * Added support for 64B completion queue entries
>>> +* **Updated hns3 driver.**
>>> +
>>> + * Added support for traffic management
>>> + Support for configuring port's peak rate and TC's peak rate with PF
>>> +
>>
>> Hi Lijun,
>>
>> Are these two different items, or second sentences is continuation of the
>> first one?
> Both the port peak rate and TC peak rate can be configured, or they can be
> configured separately.
I asked from formatting perspective. In the output html these two lines looks
like a long single line, if the intention is to have them as they are seen in
the .rst file additional formatting is required.
>>
>>> * **Updated Intel ice driver.**
>>> Updated the Intel ice driver with new features and improvements, including:
>>>
>>
>> .
>>
next prev parent reply other threads:[~2021-01-29 8:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 13:43 [dpdk-dev] [PATCH 0/3] update doc " Lijun Ou
2021-01-20 13:43 ` [dpdk-dev] [PATCH 1/3] doc: add FEC in NIC features Lijun Ou
2021-01-28 0:20 ` Ferruh Yigit
2021-01-28 0:21 ` Ferruh Yigit
2021-01-28 1:55 ` oulijun
2021-01-28 9:14 ` Thomas Monjalon
2021-01-20 13:43 ` [dpdk-dev] [PATCH 2/3] doc: update release notes for hns3 Lijun Ou
2021-01-28 0:25 ` Ferruh Yigit
2021-01-20 13:43 ` [dpdk-dev] [PATCH 3/3] doc: fix hns3 rst Lijun Ou
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 0/5] update doc for hns3 Lijun Ou
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 1/5] doc: add FEC in NIC features Lijun Ou
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 2/5] net/hns3: add FEC feature for hns3.ini Lijun Ou
2021-01-28 14:12 ` Thomas Monjalon
2021-01-29 1:13 ` oulijun
2021-01-29 8:46 ` Ferruh Yigit
2021-01-29 8:57 ` Thomas Monjalon
2021-01-29 9:10 ` oulijun
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 3/5] net/cxgbe: add FEC feature for cxgbe.ini Lijun Ou
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 4/5] doc: update release notes for hns3 Lijun Ou
2021-01-28 14:46 ` Ferruh Yigit
2021-01-29 1:28 ` oulijun
2021-01-29 8:48 ` Ferruh Yigit [this message]
2021-01-28 12:43 ` [dpdk-dev] [PATCH v2 5/5] doc: fix hns3 rst Lijun Ou
2021-01-29 9:22 ` [dpdk-dev] [PATCH v3 0/3] update doc for hns3 Lijun Ou
2021-01-29 9:22 ` [dpdk-dev] [PATCH v3 1/3] doc: add FEC in NIC features Lijun Ou
2021-01-29 9:22 ` [dpdk-dev] [PATCH v3 2/3] doc: update release notes for hns3 Lijun Ou
2021-01-29 9:22 ` [dpdk-dev] [PATCH v3 3/3] doc: fix hns3 rst Lijun Ou
2021-01-29 11:57 ` [dpdk-dev] [PATCH v3 0/3] update doc for hns3 Ferruh Yigit
2021-02-03 9:43 ` 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=3e5f308c-8dd1-4aa1-b957-05f5e2dca67d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=linuxarm@openeuler.org \
--cc=oulijun@huawei.com \
--cc=thomas@monjalon.net \
/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).