DPDK patches and discussions
 help / color / mirror / Atom feed
From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: RE: reg. Flow director rule create on LACP Bond
Date: Thu, 4 Apr 2024 05:55:06 +0000	[thread overview]
Message-ID: <PSAPR04MB55161D6323EE55B255D29726D63C2@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <PSAPR04MB55167424545EDA3401D2669DD63D2@PSAPR04MB5516.apcprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Can anyone help on the below issue , is flow create with specific pattern supported in LACP Bond?

From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Sent: Wednesday, April 3, 2024 4:14 PM
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: reg. Flow director rule create on LACP Bond

Hi All,
    I am trying to create Flow director rule to select the specific RX queue.
Example:
flow create 0 ingress pattern eth / ipv4 src is 20.20.20.2 dst is 20.20.20.5 / end actions queue index 1 / end

Tested with LINK create and applied the mentioned rule , traffic with src 20.20.20.2 and dst 20.20.20.5  pattern reaching the specified queue index .

Same rule is not working with LACP bond getting error in flow validate.
ERROR:
bond_flow_validate(77) - Operation rte_flow_validate failed for slave 0 with error -22
Is Flow director rule supported in LACP Bond ?
Am I missing something here .

Thanks in advance.


Regards,
Bala

[-- Attachment #2: Type: text/html, Size: 4437 bytes --]

      reply	other threads:[~2024-04-04  5:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 10:44 Balakrishnan K
2024-04-04  5:55 ` Balakrishnan K [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=PSAPR04MB55161D6323EE55B255D29726D63C2@PSAPR04MB5516.apcprd04.prod.outlook.com \
    --to=balakrishnan.k1@tatacommunications.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).