From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
dpdk-dev <dev@dpdk.org>,
"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
"Eads, Gage" <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 14:52:49 +0000 [thread overview]
Message-ID: <SN6PR11MB3103D9E8600ACA80B2AAD4989E170@SN6PR11MB3103.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1PC+OfUFG2nDGMNt9sXLJO2MRDC=6p6WcXPybALLQaONA@mail.gmail.com>
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Wednesday, October 28, 2020 4:36 AM
> To: McDaniel, Timothy <timothy.mcdaniel@intel.com>
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; dpdk-dev
> <dev@dpdk.org>; Carrillo, Erik G <erik.g.carrillo@intel.com>; Eads, Gage
> <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
>
> 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?
>
.max_event_queues is a uint8_t, so we could not go to 256 without changing the
data structure.
>
> > #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
> >
next prev parent reply other threads:[~2020-10-28 14:53 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
2020-10-28 14:52 ` McDaniel, Timothy [this message]
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=SN6PR11MB3103D9E8600ACA80B2AAD4989E170@SN6PR11MB3103.namprd11.prod.outlook.com \
--to=timothy.mcdaniel@intel.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=jerinjacobk@gmail.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).