DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dpdk-dev <dev@dpdk.org>
Cc: JP Lee <jongpil.lee@broadcom.com>,
	Kovacevic Marko <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5] doc: update bnxt guide
Date: Thu, 21 May 2020 14:51:39 +0100	[thread overview]
Message-ID: <65d7b9b8-b91c-aacd-3bcf-4f528f32be12@intel.com> (raw)
In-Reply-To: <CACZ4nhsm9HRejHbJmJfDHTkF-5sD5KCzrU9TmMYi61xH4w7V+A@mail.gmail.com>

On 5/21/2020 2:16 AM, Ajit Khaparde wrote:
> On Wed, May 20, 2020 at 1:04 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
> wrote:
> 
>>     - Update list of supported adapters.
>>     - Update list of supported features.
>>     - Add some details to describe the features.
>>     - Remove obsolete limitations.
>>     - Fix and update links.
>>
>> Signed-off-by: JP Lee <jongpil.lee@broadcom.com>
>> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>> Acked-by: Kovacevic Marko <marko.kovacevic@intel.com>
>> ---
>> v1->v2: Some lines were too long in v1. Made then shorter. Checked for
>> typos.
>> v2->v3: Removed list of extended stats.
>> v3->v4: Removed an irrelevant line.
>> v4->v5: Shorten the long lines further.
>>
> 
> Applied to dpdk-next-net-brcm. Thanks

Fixed build warnings [1] as following [2] while merging, please double check the
changes.

[1]
.../doc/guides/nics/bnxt.rst:127: WARNING: Bullet list ends without a blank
line; unexpected unindent.
.../doc/guides/nics/bnxt.rst:258: WARNING: Bullet list ends without a blank
line; unexpected unindent.
.../doc/guides/nics/bnxt.rst:262: WARNING: Bullet list ends without a blank
line; unexpected unindent.
.../doc/guides/nics/bnxt.rst:267: WARNING: Bullet list ends without a blank
line; unexpected unindent.
.../doc/guides/nics/bnxt.rst:270: WARNING: Bullet list ends without a blank
line; unexpected unindent.
.../doc/guides/nics/bnxt.rst:274: WARNING: Bullet list ends without a blank
line; unexpected unindent.


[2]
diff --git a/doc/guides/nics/bnxt.rst b/doc/guides/nics/bnxt.rst
index a0747d7e33..ed650187e0 100644
--- a/doc/guides/nics/bnxt.rst
+++ b/doc/guides/nics/bnxt.rst
@@ -124,9 +124,9 @@ Refer to https://doc.dpdk.org/guides/howto/flow_bifurcation.html
 Benefits of the flow bifurcation include:

 * Better performance with less CPU overhead, as user application can directly
-access the NIC for data path
+  access the NIC for data path
 * NIC is still being controlled by the kernel, as control traffic is forwarded
-only to the kernel driver
+  only to the kernel driver
 * Control commands, e.g. ethtool, will work as usual

 Running on a VF, the BXNT PMD supports the flow bifurcation with a combination
@@ -255,23 +255,23 @@ The BNXT PMD supports hardware-based packet filtering:

 * UC (Unicast) MAC Filters
     * No unicast packets are forwarded to an application except the one with
-    DMAC address added to the port
+      DMAC address added to the port
     * At initialization, the station MAC address is added to the port
 * MC (Multicast) MAC Filters
     * No multicast packets are forwarded to an application except the one with
-    MC address added to the port
+      MC address added to the port
     * When the application listens to a multicast group, it adds the MC address
-    to the port
+      to the port
 * VLAN Filtering Mode
     * When enabled, no packets are forwarded to an application except the ones
-    with the VLAN tag assigned to the port
+      with the VLAN tag assigned to the port
 * Allmulticast Mode
     * When enabled, every multicast packet received on the port is forwarded to
-    the application
+      the application
     * Typical usage is routing applications
 * Promiscuous Mode
     * When enabled, every packet received on the port is forwarded to the
-    application
+      application

 Unicast MAC Filter
 ^^^^^^^^^^^^^^^^^^

  reply	other threads:[~2020-05-21 13:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 22:03 [dpdk-dev] [PATCH] " Ajit Khaparde
2020-05-05 16:58 ` Ajit Khaparde
2020-05-06  8:57 ` Ferruh Yigit
2020-05-06 16:09   ` Ajit Khaparde
2020-05-13  9:08     ` Ferruh Yigit
2020-05-14 10:39 ` Kovacevic, Marko
2020-05-15 21:56   ` [dpdk-dev] [PATCH v2] " Ajit Khaparde
2020-05-18  9:34     ` Ferruh Yigit
2020-05-18 17:38       ` [dpdk-dev] [PATCH v3] " Ajit Khaparde
2020-05-18 17:58       ` [dpdk-dev] [PATCH v4] " Ajit Khaparde
2020-05-18 22:04         ` Ajit Khaparde
2020-05-19  8:15           ` Ferruh Yigit
2020-05-20 20:03             ` [dpdk-dev] [PATCH v5] " Ajit Khaparde
2020-05-21  1:16               ` Ajit Khaparde
2020-05-21 13:51                 ` Ferruh Yigit [this message]
2020-05-23  3:53                   ` Ajit Khaparde

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=65d7b9b8-b91c-aacd-3bcf-4f528f32be12@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=jongpil.lee@broadcom.com \
    --cc=marko.kovacevic@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).