DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix tc rule handle assignment
Date: Thu, 24 Jan 2019 11:16:00 +0000	[thread overview]
Message-ID: <AM0PR0502MB379596F246AA5E19862263ECC39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1548158746-9885-1-git-send-email-viacheslavo@mellanox.com>

Tuesday, January 22, 2019 2:06 PM, Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix tc rule handle assignment
> 
> When tc rule is created via Netlink message application can provide the
> unique rule value which can be accepted by the kernel. Than rule is managed
> with this assigned handle. It was found that kernel can reject the proposed
> handle and assign its own handle value, the rule control is lost, because
> application uses its initially prorosed rule handle and knows nothing about
> handle been repleced.
> 
> The kernel can assign handle automatically, the application can get the
> assigned handle value by specifying NLM_F_ECHO flag in Netlink message
> when rule is being created. The kernel sends back the full descriptor of rule
> and handle can be retrieved from and stored by application for further rule
> management.
> 
> Fixes: 57123c00c1b8 ("net/mlx5: add Linux TC flower driver for E-Switch
> flow")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

Applied to next-net-mlx, thanks.

      reply	other threads:[~2019-01-24 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 12:05 Viacheslav Ovsiienko
2019-01-24 11:16 ` Shahaf Shuler [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=AM0PR0502MB379596F246AA5E19862263ECC39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.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).