From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tomasz Duszynski <tdu@semihalf.com>, dev@dpdk.org
Cc: dima@marvell.com, nsamsono@marvell.com, jck@semihalf.com,
jianbo.liu@arm.com, stable@dpdk.org,
Marcin Wojtas <mw@semihalf.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/mrvl: use proper constant for Rx descriptors number
Date: Tue, 20 Mar 2018 17:28:34 +0000 [thread overview]
Message-ID: <b7616cec-fe5c-6c89-26c1-6d0b706e4c4e@intel.com> (raw)
In-Reply-To: <1521115941-17859-1-git-send-email-tdu@semihalf.com>
On 3/15/2018 12:12 PM, Tomasz Duszynski wrote:
> Since filling hardware buffer pool (bpool) is Rx related
> constant describing maximum number of rx descriptors
> instead of maximum number of Tx descriptors should be used.
>
> Fixes: 0ddc9b815b11 ("net/mrvl: add net PMD skeleton")
> Cc: stable@dpdk.org
>
> Signed-off-by: Marcin Wojtas <mw@semihalf.com>
> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-03-20 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 12:12 [dpdk-stable] " Tomasz Duszynski
2018-03-20 17:28 ` 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=b7616cec-fe5c-6c89-26c1-6d0b706e4c4e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=jck@semihalf.com \
--cc=jianbo.liu@arm.com \
--cc=mw@semihalf.com \
--cc=nsamsono@marvell.com \
--cc=stable@dpdk.org \
--cc=tdu@semihalf.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).