patches for DPDK stable branches
 help / color / Atom feed
From: Ferruh Yigit <>
To: Viacheslav Ovsiienko <>,
Subject: Re: [dpdk-stable] [PATCH v2] net/mlx5: fix matcher field usage for metadata entities
Date: Fri, 17 Jan 2020 17:18:53 +0000
Message-ID: <> (raw)
In-Reply-To: <>

On 1/17/2020 11:16 AM, Viacheslav Ovsiienko wrote:
> Matcher is flow table related structure providing the flow pattern
> to be translated directly in hardware controlling data. This structure
> includes the metadata register c0 field, that might be engaged to
> support META and MARK related flow items and actions. Also, this
> register might be used by kernel to specify the source vport index.
> In this case (if kernel uses the field) the register c0 is split
> into two 16-bit subfields - one for META/MARK items and another
> to handle vport.
> The actual configuration is queried by PMD from kernel in runtime
> and depending on the mask returned by kernel the PMD can use upper
> or lower half of register c0 field. This patch adds the missing
> support for upper half. This missed support caused the non-operational
> META/MARK items on some kernel configurations.
> Fixes: e554b672aa05 ("net/mlx5: support flow tag")
> Cc:
> Signed-off-by: Viacheslav Ovsiienko <>
> Acked-by: Matan Azrad <>
> ---
> v1:
> v2: - update log message
>     - update headline from:
>       "net/mlx5: fix register c0 usage for metadata entities"

Applied to dpdk-next-net/master, thanks.

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  7:53 [dpdk-stable] [PATCH] net/mlx5: fix register c0 " Viacheslav Ovsiienko
2020-01-06 14:48 ` Matan Azrad
2020-01-08  7:57 ` Raslan Darawsheh
2020-01-17 11:16 ` [dpdk-stable] [PATCH v2] net/mlx5: fix matcher field " Viacheslav Ovsiienko
2020-01-17 17:18   ` Ferruh Yigit [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

Archives are clonable:
	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox