From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BAF3BA053E for ; Mon, 27 Jul 2020 20:24:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 39D762B86; Mon, 27 Jul 2020 20:24:58 +0200 (CEST) Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) by dpdk.org (Postfix) with ESMTP id 2624B1023 for ; Mon, 27 Jul 2020 20:24:56 +0200 (CEST) Received: by mail-lj1-f181.google.com with SMTP id q4so18362230lji.2 for ; Mon, 27 Jul 2020 11:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0BGdzdoFFJjs1RwuPgnAoScGEqo8xFodJc3NqhumGBY=; b=On1//b3qquS5n1zZKd5d768ie3fzhX6TE4IWQIonR1y4Lt7B43WeMerlhL23Wj3svM PC+/dQcRTwyitsb9pVm7CAACyWVUa0cKNCPblgOxbn9FqVO8Rr4IK1VpTy2HI5Em5yTc VleMsrkRPb4FPwml69FLbHB1HKkiIduE1QjEX2XY75f6796ZwwcmIaYg/UyoiUKKiceG pbxGIu25LoVIHlR8S9cRrbRCiDYoB403sry0BzInPdunebvDfb03b0AsNq3TpgXh5Nk7 mOrWqmUgiJ/7yihIU7aN5A+hBBmftJgpNvfcKfa3yFhM6QoqJ5PelVIfgqmgT6TMn8Dd Xhvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0BGdzdoFFJjs1RwuPgnAoScGEqo8xFodJc3NqhumGBY=; b=O8K96wY4+GTTr+8MMDndi9SkV+qqoBbJJ2EhB76vo4F+EXavCeR8+MiZrbUyKFsPgM 1Ftbiyr3bZ3/zIUiiRELrCN1vFeHvn/BVMjeJVJ/77X+xTRO2sYemMqjylz6aPOx0U6c GUA66GjpvgGmbgjk2+npsy89kWqKm5Pc7bho9BqZXE3aOCP9OJ78J3h0+wr1bs5q42Fw 2IULmqYGH4U06rrGvLWaazGiygK8K73P0iE5JZjoFWXTH8Wdw56vgjRI+74O4vFPpAp3 U8MSbqze9+yREMGK9vsi0kRFTBC7Dwin07rq98Mx67GOzBklxu3pO6XWJoeSbdFqYIHd nfcg== X-Gm-Message-State: AOAM531l8DFXAGj3Jw5uKLw0CxrmMTsmKy+3MGKgb/vnSMpXBycANhWd q62YjoJw/ZHBG3jnbrrUEBY0ninF/KyxVRNkQcI= X-Google-Smtp-Source: ABdhPJwuAckqEmIrn8UB6mEMzRAsPQVyCoXxdFLR0uxXjWw4055t27e5LAJFUdfExOm/7B7j1PmPDj9Fi6U9cxYy5OY= X-Received: by 2002:a2e:8016:: with SMTP id j22mr10622144ljg.405.1595874295593; Mon, 27 Jul 2020 11:24:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Erez Ferber Date: Mon, 27 Jul 2020 21:24:43 +0300 Message-ID: To: Gerry Wan Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] COUNT action not supported on mlx5 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, One possible condition to get -ENOTSUP is if DevX is disabled on the NIC, Have you verified DevX is enabled ? Please check here : https://doc.dpdk.org/guides/nics/mlx5.html --- enable DevX (required by Direct Rules and other features): UCTX_EN=1 --- With higher log verbosity, you could check in the application initialization if mlx5 PMD returns"DevX is supported" to make sure. Regards, Erez On Mon, 27 Jul 2020 at 21:12, Gerry Wan wrote: > Hello, > > I'm trying to query per-flow statistics using RTE_FLOW_ACTION_TYPE_COUNT on > a Mellanox ConnectX-5 port. I tried extending the flow_filtering sample > application with: > > struct rte_flow_query_count count = { > .reset = 1, > .hits_set = 1, > .bytes_set = 1, > .hits = 0, > .bytes = 0, > }; > > // set attr, pattern, etc. > > action[0].type = RTE_FLOW_ACTION_TYPE_COUNT; > action[0].conf = &count; > action[1].type = RTE_FLOW_ACTION_TYPE_QUEUE; > action[1].conf = &queue; > action[2].type = RTE_FLOW_ACTION_TYPE_END; > > The call to rte_flow_validate() returns with -ENOTSUP, saying the flow > cannot be created because the count action is not supported. However, mlx5 > documentation (https://doc.dpdk.org/guides/nics/mlx5.html#statistics) > states that it does indeed support attaching count actions. Without the > count action the flow rule configuration works fine. > > I am using DPDK-20.05 and MLNX_OFED_LINUX-5.0-2.1.8.0, with a ConnectX-5 > Virtual Function (could the VF be the issue?). What can be the cause of > this? > > On a related note, is there any plan for mlx5 to support > RTE_FLOW_ITEM_TYPE_RAW? > > Thanks, >