From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rafal Kozik <rk@semihalf.com>, dev@dpdk.org
Cc: mw@semihalf.com, mk@semihalf.com, gtzalik@amazon.com,
evgenys@amazon.com, matua@amazon.com, igorch@amazon.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/ena: fix counting of per-queue number of Tx pkts
Date: Thu, 6 Jun 2019 15:33:57 +0100 [thread overview]
Message-ID: <ba762a5a-7fd4-848f-4e18-f46e46a0f0a9@intel.com> (raw)
In-Reply-To: <1557832286-15487-1-git-send-email-rk@semihalf.com>
On 5/14/2019 12:11 PM, Rafal Kozik wrote:
> Instead of counting number of used NIC Tx bufs just count number
> of Tx packets.
>
> Fixes: 45b6d86184fc ("net/ena: add per-queue software counters stats")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rafal Kozik <rk@semihalf.com>
> Acked-by: Michal Krawczyk <mk@semihalf.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-06 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 11:11 [dpdk-stable] " Rafal Kozik
2019-06-06 14:33 ` Ferruh Yigit [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=ba762a5a-7fd4-848f-4e18-f46e46a0f0a9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=matua@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=rk@semihalf.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).