From: fwefew 4t4tg <7532yahoo@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Is there a way to instruct NIC/DPDK which RXQ to deliver a packet to not RSS?
Date: Fri, 23 Dec 2022 10:30:11 -0500 [thread overview]
Message-ID: <CA+Tq66WqzOUCjt=9Dx15qZsT_RE=ZDJmSPdeppK7gWYGNMFcYg@mail.gmail.com> (raw)
In-Reply-To: <20221218141402.52240242@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
>RSS should be implemented in hardware. So it shouldn't be causing added
>latency. What device are you using.
My error; aggregate performance is the same. H/W RSS is fine.
>Packet direction to queue in HW is done with rte_flow (if your NIC
supports it)
>https://doc.dpdk.org/guides/prog_guide/rte_flow.html
Thank you! That was not on my radar for some reason. Much appreciated.
On Sun, Dec 18, 2022 at 5:14 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Sun, 18 Dec 2022 16:41:13 -0500
> fwefew 4t4tg <7532yahoo@gmail.com> wrote:
>
> > I am aware of RSS; I coded it and have gotten it to work between
> machines.
> >
> > However, the elapsed time per packet increases from <100ns/packet RSS-OFF
> > to 700-800ns RSS-ON in my test setup.
> >
> > In my scenario I have hardcoded routing between TXQs on client machines
> and
> > RXQs on the server machines.
>
> Packet direction to queue in HW is done with rte_flow (if your NIC
> supports it)
> https://doc.dpdk.org/guides/prog_guide/rte_flow.html
>
> RSS should be implemented in hardware. So it shouldn't be causing added
> latency. What device are you using.
>
[-- Attachment #2: Type: text/html, Size: 1810 bytes --]
prev parent reply other threads:[~2022-12-23 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 21:41 fwefew 4t4tg
2022-12-18 22:14 ` Stephen Hemminger
2022-12-23 15:30 ` fwefew 4t4tg [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='CA+Tq66WqzOUCjt=9Dx15qZsT_RE=ZDJmSPdeppK7gWYGNMFcYg@mail.gmail.com' \
--to=7532yahoo@gmail.com \
--cc=stephen@networkplumber.org \
--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).