From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] af_packet: allow configuring number of rings
Date: Thu, 27 Feb 2020 17:20:45 +0000 [thread overview]
Message-ID: <1f26ad63-0ec5-c463-1822-aac01004e72d@intel.com> (raw)
In-Reply-To: <20200224231117.16354-1-stephen@networkplumber.org>
On 2/24/2020 11:11 PM, Stephen Hemminger wrote:
> The maximum number of rings in af_packet is hard coded as 16.
> The user should be able to configure this as part of DPDK config.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> config/common_base | 1 +
> drivers/net/af_packet/rte_eth_af_packet.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/config/common_base b/config/common_base
> index 6ea9c63cc36b..dd154a474b57 100644
> --- a/config/common_base
> +++ b/config/common_base
> @@ -468,6 +468,7 @@ CONFIG_RTE_LIBRTE_VMXNET3_DEBUG_TX_FREE=n
> # Compile software PMD backed by AF_PACKET sockets (Linux only)
> #
> CONFIG_RTE_LIBRTE_PMD_AF_PACKET=n
> +CONFIG_RTE_PMD_AF_PACKET_MAX_RINGS=16
>
Not sure about adding a new config option for this.
There is already "qpairs" devarg, allocating queues dynamically, instead of
using a per-defined sized arrays, should enable removing
'RTE_PMD_AF_PACKET_MAX_RINGS' completely.
next prev parent reply other threads:[~2020-02-27 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 23:11 Stephen Hemminger
2020-02-27 17:20 ` Ferruh Yigit [this message]
2020-02-27 17:51 ` Stephen Hemminger
2020-02-27 17:55 ` Ferruh Yigit
2020-02-27 20:00 ` [dpdk-dev] [PATCH v2] net/af_packet: remove limitation on number of qpairs Stephen Hemminger
2020-02-27 20:56 ` John W. Linville
2020-03-02 16:24 ` Ferruh Yigit
2020-03-02 16:43 ` Stephen Hemminger
2020-03-02 17:20 ` Ferruh Yigit
2020-02-28 10:08 ` Ferruh Yigit
2020-02-28 16:52 ` John W. Linville
2020-03-02 16:17 ` Ferruh Yigit
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=1f26ad63-0ec5-c463-1822-aac01004e72d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).