DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>
Cc: dpdk-dev <dev@dpdk.org>, mattias.ronnblom@ericsson.com
Subject: Re: [dpdk-dev] eventdev DSW question
Date: Fri, 6 Dec 2019 12:18:50 +0530	[thread overview]
Message-ID: <CALBAE1O55UUf-DO+d7aHvwNg2MmJ_7_RbekHCB7RJmHVqsCgsQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ4WCtJ3+R+X6XGe+mNPEZSX__5EY-z3NSfivB_V6bO91JN-3Q@mail.gmail.com>

+ DSW maintainer


On Fri, Dec 6, 2019 at 5:57 AM Venky Venkatesh
<vvenkatesh@paloaltonetworks.com> wrote:
>
> I see that the provision in 18.11 eventdev DSW for maximum number of queues
> is
>
> #define DSW_MAX_QUEUES (16)
>
>
>
>    1. If the number of queues needed is to be increased to 7 bits (i.e.
>    128) is there any issue (correctness, scale, performance) other than
>    increased data structure size?
>    2. I see that it is only used in the following structs:
>       - struct dsw_evdev: struct dsw_queue queues[DSW_MAX_QUEUES];
>       sizeof(struct dsw_queue) ~ DSW_MAX_FLOWS. So the total increase
>       contribution here is (128-16)*DSW_MAX_FLOWS from about 0.5MB to 4MB
>       - struct dsw_port: uint64_t queue_enqueued[DSW_MAX_QUEUES],
> queue_dequeued[DSW_MAX_QUEUES];
>       This increase is negligible (a few KB at most across all dsw_ports)
>    3. So is it enough if I changed the above define? (In other words I hope
>    there are no other hidden/implicit dependencies on the current value 16
>    elsewhere in the code). Also I suppose the only way is to directly change
>    this in the code, rite?
>
> Thanks
>
> -Venky

  reply	other threads:[~2019-12-06  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  0:26 Venky Venkatesh
2019-12-06  6:48 ` Jerin Jacob [this message]
2019-12-06  8:34 ` Mattias Rönnblom
2019-12-06 16:32   ` Venky Venkatesh
2019-12-06 20:37     ` Mattias Rönnblom
2019-12-06 22:22       ` Venky Venkatesh
2019-12-07 19:35         ` Mattias Rönnblom

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=CALBAE1O55UUf-DO+d7aHvwNg2MmJ_7_RbekHCB7RJmHVqsCgsQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=vvenkatesh@paloaltonetworks.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).