From: Ferruh Yigit <ferruh.yigit@amd.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Anatoly Burakov" <anatoly.burakov@intel.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH] ethdev: refresh shared memory reference in secondary process
Date: Thu, 26 Oct 2023 14:11:06 +0100 [thread overview]
Message-ID: <4fe10600-d1ec-41f5-8348-4b9d1489b9b3@amd.com> (raw)
In-Reply-To: <20231020120629.2158219-1-david.marchand@redhat.com>
On 10/20/2023 1:06 PM, David Marchand wrote:
> In the process of releasing ethdev port in the primary process,
> secondary processes are asked to stop referencing such a port.
> Doing so, those processes can't predict whether the primary process
> will later invalidate/free the shared memory. So they may live with a
> reference to an old shared memory memzone and location in memory.
>
> Refresh the shared memory pointer in secondary process when requesting
> access to the shared memory: this is the best moment ethdev can check
> it because the primary process will (re-)create a shared memory only if
> no secondary process is referencing a ethdev port.
>
> Bugzilla ID: 1303
> Fixes: 36c46e738120 ("ethdev: cleanup shared data with the last port")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-10-26 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 12:06 David Marchand
2023-10-26 13:11 ` Ferruh Yigit [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=4fe10600-d1ec-41f5-8348-4b9d1489b9b3@amd.com \
--to=ferruh.yigit@amd.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=thomas@monjalon.net \
/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).