DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	dpdk-dev <dev@dpdk.org>,
	 Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Gage Eads <gage.eads@intel.com>,
	 "Van Haaren, Harry" <harry.van.haaren@intel.com>,
	Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/1] eventdev: increase MAX QUEUES PER DEV to 255
Date: Wed, 28 Oct 2020 15:05:55 +0530	[thread overview]
Message-ID: <CALBAE1PC+OfUFG2nDGMNt9sXLJO2MRDC=6p6WcXPybALLQaONA@mail.gmail.com> (raw)
In-Reply-To: <1603728068-1617-1-git-send-email-timothy.mcdaniel@intel.com>

On Mon, Oct 26, 2020 at 9:29 PM Timothy McDaniel
<timothy.mcdaniel@intel.com> wrote:
>
> DLB supports a total of 256 queues, 128 load balanced queues
> and 128 directed queues.
>
> Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
> ---
>  config/rte_config.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/rte_config.h b/config/rte_config.h
> index 8aa46a1..b78c6aa 100644
> --- a/config/rte_config.h
> +++ b/config/rte_config.h
> @@ -71,7 +71,7 @@
>
>  /* eventdev defines */
>  #define RTE_EVENT_MAX_DEVS 16
> -#define RTE_EVENT_MAX_QUEUES_PER_DEV 64
> +#define RTE_EVENT_MAX_QUEUES_PER_DEV 255

If it is 0..255 then this value should be 256. Isn't it?


>  #define RTE_EVENT_TIMER_ADAPTER_NUM_MAX 32
>  #define RTE_EVENT_ETH_INTR_RING_SIZE 1024
>  #define RTE_EVENT_CRYPTO_ADAPTER_MAX_INSTANCE 32
> --
> 2.6.4
>

  reply	other threads:[~2020-10-28  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 16:01 Timothy McDaniel
2020-10-28  9:35 ` Jerin Jacob [this message]
2020-10-28 14:52   ` McDaniel, Timothy
2020-10-30 20:03 ` Eads, Gage
2020-10-31 10:58   ` Jerin Jacob

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='CALBAE1PC+OfUFG2nDGMNt9sXLJO2MRDC=6p6WcXPybALLQaONA@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinj@marvell.com \
    --cc=timothy.mcdaniel@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).