From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: "Дмитрий Степанов" <stepanov.dmit@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: Flow rules performance with ConnectX-6 Dx
Date: Fri, 11 Mar 2022 11:37:15 +0000 [thread overview]
Message-ID: <BL1PR12MB5945A3B07DD85B9AB157D91BB90C9@BL1PR12MB5945.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CA+-SuJ1EqYKQdW=24+g7B0DUgUTvoO9BNy3q-zgOfZi7n8Q6kQ@mail.gmail.com>
Hi Dmitry,
Can it be that RSS, to which non-matching traffic gets by default,
is configured in a way that steers each destination IP to one queue?
And this 15 Mpps is in fact how much a core can read from a queue?
In general, it is always worth trying to reproduce the issue with testpmd
and to describe flow rules in full testpmd format ("flow create...").
next prev parent reply other threads:[~2022-03-11 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:10 Дмитрий Степанов
2022-03-11 11:37 ` Dmitry Kozlyuk [this message]
2022-03-11 12:58 ` Дмитрий Степанов
2022-03-18 14:54 ` Dmitry Kozlyuk
2022-03-21 8:40 ` Дмитрий Степанов
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=BL1PR12MB5945A3B07DD85B9AB157D91BB90C9@BL1PR12MB5945.namprd12.prod.outlook.com \
--to=dkozlyuk@nvidia.com \
--cc=stepanov.dmit@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).