From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hiroyuki Mikita <h.mikita89@gmail.com>
Cc: dev@dpdk.org, "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] sched: fix releasing enqueued packets
Date: Fri, 23 Sep 2016 21:17:05 +0200 [thread overview]
Message-ID: <2786388.9DBIDqzIBK@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D8912647A74CC9@IRSMSX108.ger.corp.intel.com>
> > rte_sched_port_free should release only enqueued packets of all queues.
> > Previous behavior is that enqueued and already dequeued packets of
> > only first 4 queues are released.
> >
> > Fixes: 61383240 ("sched: release enqueued mbufs when freeing port")
> >
> > Signed-off-by: Hiroyuki Mikita <h.mikita89@gmail.com>
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>
> Thank you!
Applied, thanks
prev parent reply other threads:[~2016-09-23 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 3:11 [dpdk-dev] [PATCH] " Hiroyuki Mikita
2016-09-05 15:15 ` [dpdk-dev] [PATCH v2] " Hiroyuki Mikita
2016-09-15 14:33 ` Dumitrescu, Cristian
2016-09-23 19:17 ` 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=2786388.9DBIDqzIBK@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=h.mikita89@gmail.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).