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 E6381A053E for ; Mon, 27 Jul 2020 20:12:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4DCB11BF7B; Mon, 27 Jul 2020 20:12:02 +0200 (CEST) Received: from mx0a-00000d04.pphosted.com (mx0a-00000d04.pphosted.com [148.163.149.245]) by dpdk.org (Postfix) with ESMTP id 11BA41BE8A for ; Mon, 27 Jul 2020 20:11:59 +0200 (CEST) Received: from pps.filterd (m0102888.ppops.net [127.0.0.1]) by mx0a-00000d04.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 06RI9pAf025887 for ; Mon, 27 Jul 2020 11:11:59 -0700 Received: from mx0b-00000d03.pphosted.com (mx0b-00000d03.pphosted.com [148.163.153.234]) by mx0a-00000d04.pphosted.com with ESMTP id 32gh49y26f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 27 Jul 2020 11:11:59 -0700 Received: from pps.filterd (m0206578.ppops.net [127.0.0.1]) by mx0a-00000d03.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 06RI2IO5015618 for ; Mon, 27 Jul 2020 11:11:58 -0700 Received: from mx0b-00000d06.pphosted.com (mx0b-00000d06.pphosted.com [148.163.139.119]) by mx0a-00000d03.pphosted.com with ESMTP id 32gjvvyt8u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 27 Jul 2020 11:11:58 -0700 Received: from pps.filterd (m0167937.ppops.net [127.0.0.1]) by mx0b-00000d06.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 06RI3JwL024332 for ; Mon, 27 Jul 2020 11:11:57 -0700 Received: from smtp.stanford.edu (smtp4.stanford.edu [171.67.219.72]) by mx0b-00000d06.pphosted.com with ESMTP id 32gk1va2qe-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 27 Jul 2020 11:11:57 -0700 Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: gerryw) by smtp.stanford.edu (Postfix) with ESMTPSA id B9EC121C2F for ; Mon, 27 Jul 2020 11:11:56 -0700 (PDT) Received: by mail-oi1-f176.google.com with SMTP id w17so15122029oie.6 for ; Mon, 27 Jul 2020 11:11:56 -0700 (PDT) X-Gm-Message-State: AOAM531lQmhVki4gfjmpa6sYKghC2lsXMN4BIMceWCKEYpc6z2S2jArk rdG07tDIvDbO1GD+7DMoWirfkpMJz12MTZjT6EE= X-Google-Smtp-Source: ABdhPJycFmPtHfJki56qAxdhmDAqZmBTGix0OlASDzk34R0wf4Wo/6ssQcwpm+zyj3Wy/aSLhHJ/gUUIIXNBWwhvFmA= X-Received: by 2002:aca:3883:: with SMTP id f125mr453211oia.27.1595873515821; Mon, 27 Jul 2020 11:11:55 -0700 (PDT) MIME-Version: 1.0 From: Gerry Wan Date: Mon, 27 Jul 2020 11:11:45 -0700 X-Gmail-Original-Message-ID: Message-ID: To: users@dpdk.org x-proofpoint-stanford-dir: outbound X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-27_13:2020-07-27, 2020-07-27 signatures=0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-27_13:2020-07-27, 2020-07-27 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 malwarescore=0 clxscore=1015 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 phishscore=0 priorityscore=1501 spamscore=0 mlxscore=0 impostorscore=0 adultscore=100 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2007270123 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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" 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,