From: David Marchand <david.marchand@redhat.com>
To: Volodymyr Fialko <vfialko@marvell.com>
Cc: dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
jerinj@marvell.com, anoobj@marvell.com, stable@dpdk.org
Subject: Re: [PATCH v2] reorder: fix registration of dynamic field in mbuf
Date: Thu, 16 Mar 2023 16:55:41 +0100 [thread overview]
Message-ID: <CAJFAV8w9fayCyJwuiZ=HFrLwOB-tvo3h1Qz4J2yVpjjacej+8g@mail.gmail.com> (raw)
In-Reply-To: <20230313130428.2650232-1-vfialko@marvell.com>
On Mon, Mar 13, 2023 at 2:05 PM Volodymyr Fialko <vfialko@marvell.com> wrote:
>
> It's possible to initialize reorder buffer with user allocated memory via
> rte_reorder_init() function. In such case rte_reorder_create() is not
> required and reorder dynamic field in rte_mbuf will not be registered.
>
> Both reorder lib and mbuf dynamic field are using `rte_mcfg_tailq`
> read/write lock for synchronization, to avoid deadlocking move reorder
> buffer initialization before queue insertion.
>
> Fixes: 01f3496695b5 ("reorder: switch sequence number to dynamic mbuf field")
> Cc: stable@dpdk.org
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
Applied, thanks Volodymyr.
--
David Marchand
next prev parent reply other threads:[~2023-03-16 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230313093450.2560058-1-vfialko@marvell.com>
2023-03-13 13:04 ` Volodymyr Fialko
2023-03-15 15:29 ` Volodymyr Fialko
2023-03-15 15:43 ` David Marchand
2023-03-15 15:46 ` Pattan, Reshma
2023-03-16 15:36 ` David Marchand
2023-03-16 15:55 ` David Marchand [this message]
2023-03-13 12:59 Volodymyr Fialko
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='CAJFAV8w9fayCyJwuiZ=HFrLwOB-tvo3h1Qz4J2yVpjjacej+8g@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=vfialko@marvell.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).