From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0139542D76; Wed, 28 Jun 2023 01:12:58 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CB2C8406B3; Wed, 28 Jun 2023 01:12:58 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 1504D40151 for ; Wed, 28 Jun 2023 01:12:57 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 9A55F5C011C; Tue, 27 Jun 2023 19:12:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 27 Jun 2023 19:12:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1687907574; x=1687993974; bh=fwdyFAiab/Q1ylG2cFGs3HWINmCY/gBRVpA c9Sw9We0=; b=ItFGl7vQq4KLoBfSH5rj46Jx0zkspROo7SiV/T6HZGT8kYd08WL I4d+NkutPOV0RNYA61fKNmJxvnI2kphDJOSuLGqBI326Xb8veIbQG3ddjEyx3OTF ujae6GcoKETlIUP2PRzVr+aTTAwpzW4bwoGi0xMniYmqkjlGoaAoqMdjZrM618mw lkqqbZGE/L29ybm2lC2yuluNsADjiYFuzs9pdjVaLBlNIS2phIONgP6BSMNjVTuK sUO/IlJGJNkijRenu3t6gkbGPgeTOup6uQjbFYm4mSzoVdUsu87q3mG6+9K9UKPk uAYN2+qvymt2A3jTIikdVeWRMqFIBaRH2sA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1687907574; x=1687993974; bh=fwdyFAiab/Q1ylG2cFGs3HWINmCY/gBRVpA c9Sw9We0=; b=OBbNs9aK8KEdvhPHsG4e1Yf3aQuNXpdn1P+udZBsYt2nfq8CksO SaVVoa31jMhLisBhNO1fS440r8PmhwWSWNzAzJRYKhSwWtBgQqkvfe/YL+KbkaMo zj4ao606NuxXla8uuJ/RfYpBlz7in50ywTUVPtM8CbBLwRRtU3fTRxKCtlqHgy99 Ko0w+a8hyCEaEHWl1klDe0tXcEvAN2sVy5T3SYmXYEhY8ypGU44k+6npbI681DrY VrjO1dss0/yMxi4ue9HVEALEftjycv0QSkwhnqpvT2KwPRwk0O4WfgxjQOuyq3IV cENthou1C3uRhGRpGok5jSF5c1TeK3OIMDw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrtddugddulecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 27 Jun 2023 19:12:53 -0400 (EDT) From: Thomas Monjalon To: ferruh.yigit@amd.com, lihuisong@huawei.com, Dongdong Liu Cc: dev@dpdk.org, andrew.rybchenko@oktetlabs.ru Subject: Re: [PATCH v2 2/2] net/hns3: add FDIR VLAN match mode runtime config Date: Wed, 28 Jun 2023 01:12:51 +0200 Message-ID: <16389153.hlxOUv9cDv@thomas> In-Reply-To: <20230627071126.17161-3-liudongdong3@huawei.com> References: <20230626124332.28157-1-liudongdong3@huawei.com> <20230627071126.17161-1-liudongdong3@huawei.com> <20230627071126.17161-3-liudongdong3@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 27/06/2023 09:11, Dongdong Liu: > +- ``fdir_vlan_match_mode`` (default `strict`) > + > + Used to select VLAN match mode. This runtime config can be `strict` > + or `nostrict` and is only valid for PF drives. drives? Do you mean devices? > + If driver works on `strict` mode (default mode), hardware does strictly > + match the input flow base on VLAN number. > + > + For the following scenarios with two rules: > + > + .. code-block:: console > + > + rule0: > + pattern: eth type is 0x0806 > + actions: queue index 3 > + rule1: > + pattern: eth type is 0x0806 / vlan vid is 20 > + actions: queue index 4 > + > + If application select `strict` mode, only the ARP packets with VLAN > + 20 are directed to queue 4, and the ARP packets with other VLAN ID > + cannot be directed to the specified queue. If application want to all > + ARP packets with or without VLAN to be directed to the specified queue, > + application can select `nostrict` mode and just need to set rule0. As it is done in the rest of the document, you should use double backquotes for values of the devargs.