DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Mike Baucom <michael.baucom@broadcom.com>,
	 Lance Richardson <lance.richardson@broadcom.com>,
	 Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/bnxt: fix mark handling to check metafmt not metadata
Date: Fri, 1 May 2020 15:02:47 -0700	[thread overview]
Message-ID: <CACZ4nhuRUrUAV5nzXNEPHa4gd6OH+rpOBfPat61CED5chCn5WA@mail.gmail.com> (raw)
In-Reply-To: <20200501191616.62325-1-ajit.khaparde@broadcom.com>

On Fri, May 1, 2020 at 12:16 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:

> From: Mike Baucom <michael.baucom@broadcom.com>
>
> The current mark handling uses the meta data field of the rxcmp as the
> first level check for determining gfid vs lfid.  When the meta data is
> zero due to only the lowest 16bits of the gfid being set, the cfa code
> is incorrectly interpreted as being an lfid.  Changing code to look at
> meta fmt instead of the meta data directly for the determination.
>
> Fixes: b87abb2e55cb ("net/bnxt: support marking packet")
>
> Signed-off-by: Mike Baucom <michael.baucom@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: Lance Richardson <lance.richardson@broadcom.com>
> --
> v1->v2: fixed the commit log.
> ---
>  drivers/net/bnxt/bnxt_rxr.c | 85 ++++++++++++++++++++++---------------
>  drivers/net/bnxt/bnxt_rxr.h |  2 +
>  2 files changed, 53 insertions(+), 34 deletions(-)
>
> Patch applied to dpdk-next-net-brcm.

      reply	other threads:[~2020-05-01 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 20:39 [dpdk-dev] [PATCH] net/bnxt: mark handling needs to look at meta_fmt instead of meta data Venkat Duvvuru
2020-05-01 19:16 ` [dpdk-dev] [PATCH v2] net/bnxt: fix mark handling to check metafmt not metadata Ajit Khaparde
2020-05-01 22:02   ` Ajit Khaparde [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=CACZ4nhuRUrUAV5nzXNEPHa4gd6OH+rpOBfPat61CED5chCn5WA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.com \
    --cc=michael.baucom@broadcom.com \
    --cc=venkatkumar.duvvuru@broadcom.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).