DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>,
	jerinj@marvell.com, anoobj@marvell.com,
	Volodymyr Fialko <vfialko@marvell.com>,
	David Marchand <david.marchand@redhat.com>,
	bruce.richardson@intel.com, konstantin.v.ananyev@yandex.ru,
	john.mcnamara@intel.com
Subject: Re: [PATCH 0/2] lib/reorder: fix drain/free issues
Date: Tue, 07 Feb 2023 12:18:31 +0100	[thread overview]
Message-ID: <1872201.eGJsNajkDb@thomas> (raw)
In-Reply-To: <CAJFAV8x93byZQug0-5jccAH5ircdnejv4UT50rNdsZsSAw76qQ@mail.gmail.com>

Pïng for review

26/01/2023 16:47, David Marchand:
> Hi Reshma,
> 
> On Sat, Jan 7, 2023 at 4:20 PM Volodymyr Fialko <vfialko@marvell.com> wrote:
> >
> > This patch address issues with reorder drain/free,
> > discovered with enabled `RTE_LIBRTE_MEMPOOL_DEBUG`.
> >
> > Volodymyr Fialko (2):
> >   reorder: invalidate buf from ready queue in drain
> >   test/reorder: fix double free of drained buffers
> >
> >  app/test/test_reorder.c   | 2 ++
> >  lib/reorder/rte_reorder.c | 1 +
> >  2 files changed, 3 insertions(+)
> 
> Please review, thanks.




  reply	other threads:[~2023-02-07 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 15:19 Volodymyr Fialko
2023-01-07 15:19 ` [PATCH 1/2] reorder: invalidate buf from ready queue in drain Volodymyr Fialko
2023-02-07 16:24   ` Stephen Hemminger
2023-01-07 15:19 ` [PATCH 2/2] test/reorder: fix double free of drained buffers Volodymyr Fialko
2023-01-26 15:51   ` David Marchand
2023-02-07 16:25   ` Stephen Hemminger
2023-01-26 15:47 ` [PATCH 0/2] lib/reorder: fix drain/free issues David Marchand
2023-02-07 11:18   ` Thomas Monjalon [this message]
2023-02-06 15:47 ` Volodymyr Fialko
2023-02-19 23:19 ` 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=1872201.eGJsNajkDb@thomas \
    --to=thomas@monjalon.net \
    --cc=anoobj@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=reshma.pattan@intel.com \
    --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).