DPDK usage discussions
 help / color / mirror / Atom feed
From: "Дмитрий Степанов" <stepanov.dmit@gmail.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Flow rules performance with ConnectX-6 Dx
Date: Mon, 21 Mar 2022 11:40:48 +0300	[thread overview]
Message-ID: <CA+-SuJ1E9HxU6K8Ci_FurdoXiEJh20o7ZiW9DJnuBP8vbK8S8Q@mail.gmail.com> (raw)
In-Reply-To: <BL1PR12MB5945C4BE6730900C649D2970B9139@BL1PR12MB5945.namprd12.prod.outlook.com>

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

For some reasons I'm not able to create group 1 / jump action. I get this
error:

testpmd> flow create 0 ingress pattern end actions jump group 1 / end
port_flow_complain(): Caught PMD error type 16 (specific action): cannot
create jump action.: Operation not supported
testpmd> flow create 0 ingress group 1 pattern eth / ipv4 dst is 10.0.0.2 /
end actions drop / end
port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot
get table: Cannot allocate memory

This looks similar to
https://www.mail-archive.com/dev@dpdk.org/msg152132.html
I've checked UCTX_EN bit - and it its already set within NIC:

mstconfig -d 0000:c1:00.0 q | grep UCTX_EN
         UCTX_EN                             True(1)



пт, 18 мар. 2022 г. в 17:54, Dmitry Kozlyuk <dkozlyuk@nvidia.com>:

> Hi Dmitry,
>
> Can you check if the issue reproduces for you when using group 1?
> Group 0 is special for mlx5, its behavior differs from other groups.
> In testpmd terms:
>
> flow create 0 ingress pattern end actions jump group 1 / end
> flow create 0 ingress group 1 pattern eth / ipv4 dst is 10.0.0.2 / end
> actions drop / end
>

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

      reply	other threads:[~2022-03-21  8:41 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
2022-03-11 12:58   ` Дмитрий Степанов
2022-03-18 14:54     ` Dmitry Kozlyuk
2022-03-21  8:40       ` Дмитрий Степанов [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+-SuJ1E9HxU6K8Ci_FurdoXiEJh20o7ZiW9DJnuBP8vbK8S8Q@mail.gmail.com \
    --to=stepanov.dmit@gmail.com \
    --cc=dkozlyuk@nvidia.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).