From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: Olivier Matz <olivier.matz@6wind.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "stable@dpdk.org" <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 1/2] mempool: make event callbacks process-private
Date: Thu, 22 Sep 2022 07:31:09 +0000 [thread overview]
Message-ID: <BL1PR12MB5945B57FD45667D3468051EBB94E9@BL1PR12MB5945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220808094236.3395516-2-dkozlyuk@nvidia.com>
> From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> Sent: Monday, August 8, 2022 12:43 PM
> To: dev@dpdk.org
> Cc: Olivier Matz <olivier.matz@6wind.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; stable@dpdk.org
> Subject: [PATCH 1/2] mempool: make event callbacks process-private
>
> Callbacks for mempool events were registered in a process-shared tailq.
> This was inherently incorrect because the same function
> may be loaded to a different address in each process.
> Make the tailq process-private.
> Use the EAL tailq lock to reduce the number of different locks
> this module operates.
>
> Fixes: da2b9cb25e5f ("mempool: add event callbacks")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Kind reminder to the mempool maintainers.
next prev parent reply other threads:[~2022-09-22 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 9:42 [PATCH 0/2] common/mlx5: fix multi-process mempool registration Dmitry Kozlyuk
2022-08-08 9:42 ` [PATCH 1/2] mempool: make event callbacks process-private Dmitry Kozlyuk
2022-08-28 18:33 ` Slava Ovsiienko
2022-10-10 8:02 ` Andrew Rybchenko
2022-09-22 7:31 ` Dmitry Kozlyuk [this message]
2022-08-08 9:42 ` [PATCH 2/2] common/mlx5: fix multi-process mempool registration Dmitry Kozlyuk
2022-08-28 18:34 ` Slava Ovsiienko
2022-10-10 13:20 ` [PATCH 0/2] " Thomas Monjalon
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=BL1PR12MB5945B57FD45667D3468051EBB94E9@BL1PR12MB5945.namprd12.prod.outlook.com \
--to=dkozlyuk@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
/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).