DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] config:enlarge the default value of	RTE_MAX_QUEUES_PER_PORT to 1024
Date: Mon, 1 Jun 2015 01:00:09 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A86DC27@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1432776978-24998-1-git-send-email-jijiang.liu@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jijiang Liu
> Sent: Thursday, May 28, 2015 9:36 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] config:enlarge the default value of
> RTE_MAX_QUEUES_PER_PORT to 1024
> 
> The default value of RTE_MAX_QUEUES_PER_PORT is 256, which is too small for
> some configurations for i40e. There will return an error when configured queue
> number is larger than 256 in
> 
> rte_eth_dev_configure().
> 
> For example, in vHost sample, PF queue number: 64, configured vmdq pool
> number: 63, each vmdq pool has 4 queues, there will be required 316 queues in a
> port.
> 
> 
> Signed-off-by: Jijiang Liu <jijiang.liu@intel.com>
Acked-by: Helin Zhang <helin.zhang@intel.com>

> ---
>  config/common_bsdapp   |    2 +-
>  config/common_linuxapp |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/config/common_bsdapp b/config/common_bsdapp index
> c2374c0..0b169c8 100644
> --- a/config/common_bsdapp
> +++ b/config/common_bsdapp
> @@ -137,7 +137,7 @@ CONFIG_RTE_LIBRTE_KVARGS=y
> CONFIG_RTE_LIBRTE_ETHER=y  CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=n
>  CONFIG_RTE_MAX_ETHPORTS=32
> -CONFIG_RTE_MAX_QUEUES_PER_PORT=256
> +CONFIG_RTE_MAX_QUEUES_PER_PORT=1024
>  CONFIG_RTE_LIBRTE_IEEE1588=n
>  CONFIG_RTE_ETHDEV_QUEUE_STAT_CNTRS=16
>  CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y
> diff --git a/config/common_linuxapp b/config/common_linuxapp index
> 0078dc9..5deb55a 100644
> --- a/config/common_linuxapp
> +++ b/config/common_linuxapp
> @@ -134,7 +134,7 @@ CONFIG_RTE_LIBRTE_KVARGS=y
> CONFIG_RTE_LIBRTE_ETHER=y  CONFIG_RTE_LIBRTE_ETHDEV_DEBUG=n
>  CONFIG_RTE_MAX_ETHPORTS=32
> -CONFIG_RTE_MAX_QUEUES_PER_PORT=256
> +CONFIG_RTE_MAX_QUEUES_PER_PORT=1024
>  CONFIG_RTE_LIBRTE_IEEE1588=n
>  CONFIG_RTE_ETHDEV_QUEUE_STAT_CNTRS=16
>  CONFIG_RTE_ETHDEV_RXTX_CALLBACKS=y
> --
> 1.7.7.6

  reply	other threads:[~2015-06-01  1:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  1:36 Jijiang Liu
2015-06-01  1:00 ` Zhang, Helin [this message]
2015-06-02 16:25   ` Thomas Monjalon
2015-09-21 16:02 Jijiang Liu

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A86DC27@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jijiang.liu@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).