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 4C66A45B94; Mon, 21 Oct 2024 18:13:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3476840285; Mon, 21 Oct 2024 18:13:13 +0200 (CEST) Received: from mail-pf1-f176.google.com (mail-pf1-f176.google.com [209.85.210.176]) by mails.dpdk.org (Postfix) with ESMTP id B750E40263 for ; Mon, 21 Oct 2024 18:13:11 +0200 (CEST) Received: by mail-pf1-f176.google.com with SMTP id d2e1a72fcca58-71e5ae69880so3624179b3a.2 for ; Mon, 21 Oct 2024 09:13:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1729527191; x=1730131991; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=3eY34RHp/kTKIVFbPBC8f8zLmzWq95x0PgGCDbuiq8U=; b=Tyt7HQCoomYemgkO0JCFkKEYJjpHsPf++NhadZaFej9eE+dkuFovvHBbyKcEJmRlv6 CqEqE1Z7tXtZC15OiwdQ6KMsV7rjEx5dt8hfVbXIZ2q6XJ4OFPGTr+FaTgPrnY5KKFwL g/lWdTckUY1elPimwEcZdeZ4MmblxarO7nWniwjVEJuIUPiLtSJd7rdi2NFHWEQ62SLo Oi90CPRsd5uYPArCAEio7VtWjhP9KhD0Xf2wvUcBWT/RxmIYtt5oC5/nA4Qy7l5RN3NX 2HPKWiLs8a+mkQ4BO7m1bc15n/LfgmDvbnzfG3E0iNXYzCaA9VVaWP5LVl0kVfVJshqD P2Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729527191; x=1730131991; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=3eY34RHp/kTKIVFbPBC8f8zLmzWq95x0PgGCDbuiq8U=; b=RICDOueVQaoxjy/Wg5f8EZBUvMO6fMMd4adowEIao4GlkDrf42EWVssBvZPQz81Bsq ct8qiGVVS3a6iTsmlcv9zuOwlF774o2S3w2C6+RC0LN8HNFh7k6o4XTuCWER0bAo8rU3 BFeTcobwz4hegOb6NkeHUM17WkuQUT9i5jGPkuKBhKxsAO1muas4yQUz8CcqPAUP0Fnr rrv7Op7rn6UYNMFwYlUdEJpWwbKkLWqPouqlf6kIMSBe4vWgnPqqrr/5b+mEKq1cxFO9 nz+8aDVjag6NzXQChMKwMpaaKoCl46aiQcIFtZcPRcTpqKOXjIt+OBw1LHCGtriTdYXe rxVw== X-Gm-Message-State: AOJu0YzjHMC1miCZGU1ajT+Iqv+T5gn6/YW1O+WuQXQMi2wLTYYOToBE OR/arAVr9F39gqRxyUmi0qWZbkvrmmScvi2UezT1AlOUCqRG2EEnOb7mjTwksxI= X-Google-Smtp-Source: AGHT+IGzF37Jw4OgoLn36chmGXNfG76Afgkvvgn8+b+fENbLyBRfaTKE7Hs6+ve1iCo6rurmAVlCLQ== X-Received: by 2002:a05:6a00:3909:b0:71e:634e:fe0d with SMTP id d2e1a72fcca58-71ea31aea56mr15104401b3a.12.1729527190701; Mon, 21 Oct 2024 09:13:10 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-71ec1332f6asm3085621b3a.69.2024.10.21.09.13.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Oct 2024 09:13:10 -0700 (PDT) Date: Mon, 21 Oct 2024 09:09:09 -0700 From: Stephen Hemminger To: Sriharsha Basavapatna Cc: dev@dpdk.org, Shuanglin Wang , Kishore Padmanabha , Ajit Khaparde Subject: Re: [PATCH v6 06/47] net/bnxt: tf_core: TF support flow scale query Message-ID: <20241021090909.55f5ce0a@hermes.local> In-Reply-To: <20241021082607.232829-7-sriharsha.basavapatna@broadcom.com> References: <20241021082607.232829-1-sriharsha.basavapatna@broadcom.com> <20241021082607.232829-7-sriharsha.basavapatna@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Mon, 21 Oct 2024 13:55:26 +0530 Sriharsha Basavapatna wrote: > From: Shuanglin Wang > > TF supports the flow scale query feature for OVS application. > The resource usage is tracked when opening a TF session > or adding/deleting a flow. The resources includes WC TCAM, > EM, Action, Counter, Meter, ACT_ENCAP, ACT_ENCAP, and SP_SMAC. > User can query the resource usage using niccli. > > Several improvements on flow scale query feature: > 1. Some default rules require both RX and TX resources; > need to update usage states on both direcitons. > 2. Update resoure usage state for regular flows only. > 3. Added a buffer dirty state to avoid unnecessary > state sync with firmware. > > This feature is disabled by default. Using the build flag > -DTF_FLOW_SCALE_QUERY to enable it. > > Signed-off-by: Shuanglin Wang > Reviewed-by: Kishore Padmanabha > Reviewed-by: Ajit Khaparde > Signed-off-by: Sriharsha Basavapatna ### [PATCH] net/bnxt: tf_core: TF support flow scale query WARNING:TYPO_SPELLING: 'direcitons' may be misspelled - perhaps 'directions'? #14: need to update usage states on both direcitons. ^^^^^^^^^^ WARNING:TYPO_SPELLING: 'resoure' may be misspelled - perhaps 'resource'? #15: 2. Update resoure usage state for regular flows only. ^^^^^^^ WARNING:LONG_LINE_COMMENT: line length of 296 exceeds 120 columns #220: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:23264: +/* Common structure to cast crypto key split entries. This casting is required in the following HWRM command inputs/outputs if the backing store type is TX_CK or RX_CK. 1. hwrm_func_backing_store_cfg_v2_input 2. hwrm_func_backing_store_qcfg_v2_output 3. hwrm_func_backing_store_qcaps_v2_output */