From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix VXLAN port registration race condition
Date: Thu, 24 Jan 2019 11:16:38 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795AA97DA1D753594070F27C39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1548249558-15783-1-git-send-email-viacheslavo@mellanox.com>
Wednesday, January 23, 2019 3:19 PM, Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH v2] net/mlx5: fix VXLAN port registration race
> condition
>
> E-Switch VXLAN tunneling rules require virtual VXLAN network devices be
> created. These devices are managed by MLX5 PMD and created/deleted
> dynamically.
>
> Kernel creates the VXLAN devices and registers VXLAN UDP ports to be
> hardware offloaded within the NIC kernel drivers. The registration process is
> being performed into context of working kernel thread and the race
> conditions might happen.
>
> The VXLAN device is created and success code is returned to calling
> application, but the UDP port registration process is not completed yet and
> the next applied rule might be rejected by the driver with ENOSUP code. This
> patch adds some timeout for new created devices, allowing port registration
> process to be completed. The waiting is performed once after device been
> created and first rule is being applied.
>
> Fixes: 95a464cecc21 ("net/mlx5: add E-switch VXLAN tunnel devices
> management")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2019-01-24 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 7:51 [dpdk-dev] [PATCH] " Viacheslav Ovsiienko
2019-01-23 13:19 ` [dpdk-dev] [PATCH v2] " 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=AM0PR0502MB3795AA97DA1D753594070F27C39A0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@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).