From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>, Ori Kam <orika@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix E-Switch flow without port item
Date: Wed, 1 May 2019 06:09:56 +0000 [thread overview]
Message-ID: <AM0PR0502MB379501205D945C8B73D0C4E2C33B0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <D8363820-8BD2-405F-B862-0443749D929E@mellanox.com>
Thursday, April 25, 2019 8:54 PM, Yongseok Koh:
> Subject: Re: [PATCH v2] net/mlx5: fix E-Switch flow without port item
>
>
>
> > On Apr 25, 2019, at 5:20 AM, Ori Kam <orika@mellanox.com> wrote:
> >
> > When creating a flow rule without the port_id pattern item, always the
> > PF was selected.
> >
> > This commit fixes this issue, if no port_id pattern item is available
> > then we use the port that the flow was created on as source port.
> >
> > Fixes: 822fb3195348 ("net/mlx5: add port id item to Direct Verbs")
> >
> > Signed-off-by: Ori Kam <orika@mellanox.com>
> > ---
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
Applied to next-net-mlx, thanks.
next prev parent reply other threads:[~2019-05-01 6:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 11:19 [dpdk-dev] [PATCH] " Ori Kam
2019-04-23 11:19 ` Ori Kam
2019-04-23 21:03 ` Yongseok Koh
2019-04-23 21:03 ` Yongseok Koh
2019-04-25 7:02 ` Ori Kam
2019-04-25 7:02 ` Ori Kam
2019-04-25 17:53 ` Yongseok Koh
2019-04-25 17:53 ` Yongseok Koh
2019-04-25 12:20 ` [dpdk-dev] [PATCH v2] " Ori Kam
2019-04-25 12:20 ` Ori Kam
2019-04-25 17:54 ` Yongseok Koh
2019-04-25 17:54 ` Yongseok Koh
2019-05-01 6:09 ` Shahaf Shuler [this message]
2019-05-01 6:09 ` Shahaf Shuler
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=AM0PR0502MB379501205D945C8B73D0C4E2C33B0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=yskoh@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).