DPDK usage discussions
 help / color / mirror / Atom feed
From: Tom Barbette <tom.barbette@uclouvain.be>
To: "Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>,
	"Aisenur Yoldaş" <aisenur.yoldas@b-ulltech.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Number of Flows
Date: Mon, 26 Jun 2023 06:16:45 +0000	[thread overview]
Message-ID: <a9d05385-8b6f-d475-738b-f9f18fd1dc34@uclouvain.be> (raw)
In-Reply-To: <20230525121316.0c7e1046@sovereign>


[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]

A few pointers here : 
https://dejankosticgithub.github.io/documents/publications/nicbench-pam21.pdf



Le 25-05-23 à 11:13, Dmitry Kozlyuk a écrit :
> 2023-05-25 10:09 (UTC+0300), Aisenur Yoldaş:
>> Hi,
>> I am trying to learn the maximum number of flow rules I can generate for my card, is there a way to learn that
>> My card is Mellanox Technologies MT27710 Family [ConnectX-4 Lx] and
>> I am using dpdk-23.03
> Hi,
>
> The maximum number of flow rules depends on the flow rules:
> * which item and action types are used
> * what flow rule attributes are used
> * what are the values in item and action data (rare case)
>
> You can estimate on real HW using app/flow-perf.
> It will also give you other useful figures,
> like memory consumption and flow rule insertion/deletion speed.
>
>

[-- Attachment #1.2: Type: text/html, Size: 1647 bytes --]

[-- Attachment #2: Signature cryptographique S/MIME --]
[-- Type: application/pkcs7-signature, Size: 5774 bytes --]

      reply	other threads:[~2023-06-26  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  7:09 Aisenur Yoldaş
2023-05-25  9:13 ` Dmitry Kozlyuk
2023-06-26  6:16   ` Tom Barbette [this message]

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=a9d05385-8b6f-d475-738b-f9f18fd1dc34@uclouvain.be \
    --to=tom.barbette@uclouvain.be \
    --cc=aisenur.yoldas@b-ulltech.com \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=users@dpdk.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).