DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: dev@dpdk.org, Ori Kam <orika@mellanox.com>,
	Matan Azrad <matan@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix default mark copy flow
Date: Wed, 27 Nov 2019 16:16:29 +0100	[thread overview]
Message-ID: <2634349.oQx4JvFnxE@xps> (raw)
In-Reply-To: <AM4PR05MB3425621B787158EAC76F44D0DB440@AM4PR05MB3425.eurprd05.prod.outlook.com>

27/11/2019 14:45, Ori Kam:
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Wednesday, November 27, 2019 3:37 PM
> 
> > In extensive metadata mode the MARK copy table is engaged,
> > if the application creates the flow with zero MARK ID action:
> > 
> > flow create 1 ingress pattern eth / ... / end actions mark id 0 / .. end
> > 
> > And then destroys that, the traffic to the port stops. This happens
> > due to default flow for the copy table has the zero ID and is removed
> > with the application rule. The patch extends internal ID variable
> > to 64 bits and provide the UINT64_MAX ID for the copy table default
> > rule.
> > 
> > Fixes: dd3c774f6ffb ("net/mlx5: add metadata register copy table")
> > 
> > Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Acked-by: Ori Kam <orika@mellanox.com>

Applied, thanks




      reply	other threads:[~2019-11-27 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 13:36 Viacheslav Ovsiienko
2019-11-27 13:45 ` Ori Kam
2019-11-27 15:16   ` Thomas Monjalon [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=2634349.oQx4JvFnxE@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --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).