From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, "Hunt, David" <david.hunt@intel.com>
Subject: Re: [dpdk-dev] [PATCH] event/sw: fix credit return on invalid queue id
Date: Thu, 20 Apr 2017 00:27:24 +0200 [thread overview]
Message-ID: <3221074.Fui6N1Oart@xps> (raw)
In-Reply-To: <d71a534e-adc8-3593-cbc3-0290592dbce9@intel.com>
18/04/2017 12:11, Hunt, David:
> On 18/4/2017 10:58 AM, Harry van Haaren wrote:
> > This patch returns a credit when an rte_event is
> > enqueued with an invalid queue_id. Previously a
> > credit was leaked from the system.
> >
> > Note that the eventdev instance does not attempt
> > to free any resources that the rte_event owns. As
> > a result, resources owned by the rte_event are leaked.
> > Eg. if the rte_event represents an rte_mbuf, the mbuf
> > will not be freed, and causes a leak from the mempool.
> >
> > Fixes: 656af9180014 ("event/sw: add worker core functions")
> >
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> Acked-by: David Hunt <david.hunt@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-04-19 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 9:58 Harry van Haaren
2017-04-18 10:11 ` Hunt, David
2017-04-19 22:27 ` Thomas Monjalon [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=3221074.Fui6N1Oart@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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).