From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2A2EBC433F5 for ; Mon, 14 Feb 2022 13:41:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232145AbiBNNl5 (ORCPT ); Mon, 14 Feb 2022 08:41:57 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55518 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354511AbiBNNly (ORCPT ); Mon, 14 Feb 2022 08:41:54 -0500 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 368CEB849 for ; Mon, 14 Feb 2022 05:41:46 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 178035C007F; Mon, 14 Feb 2022 08:41:44 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 14 Feb 2022 08:41:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date: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; bh=WwQWSbZAOWwyoj/cA sf2jBtYg9z6KhLN1lGVrzwGN40=; b=LWK3qTijKasxJvT2Z9VGVs8+alT5bj8ia N2x7Q4DzmBALkPrBz1QwKaJ9E2k3xIdcNF0Yr8+2fbif/2lud/IE/cOAlD3X1KdQ y+fVsuw2oTjg0PeuaX6N+msKfJfbisENyRmWozlWtMIFMmJaL6V2NOiGzh7cPbVU I+bRafIufsDsVc8/t/4wrQurjWyNAEI0KvqfoV8C4GH1hdOhHTUuFulhGdLkbqrK XCklz3630/+ziH8PMcY3gFv5GW1xrnaSsuQRcgroIdJpcGb1mxIQNgUbZJ56CG0l 6f02iufhb96wNdTWt+UXXq2etmDHhzsiTM4h4fI978vHfj91k1Sow== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjedvgdehudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepkfguohcuufgt hhhimhhmvghluceoihguohhstghhsehiughoshgthhdrohhrgheqnecuggftrfgrthhtvg hrnheptdffkeekfeduffevgeeujeffjefhtefgueeugfevtdeiheduueeukefhudehleet necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepihguoh hstghhsehiughoshgthhdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 14 Feb 2022 08:41:43 -0500 (EST) Date: Mon, 14 Feb 2022 15:41:38 +0200 From: Ido Schimmel To: Jianbo Liu Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@nvidia.com, idosch@nvidia.com, ozsh@nvidia.com, roid@nvidia.com Subject: Re: [PATCH net-next 0/2] flow_offload: add tc police parameters Message-ID: References: <20220214100922.13004-1-jianbol@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220214100922.13004-1-jianbol@nvidia.com> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Feb 14, 2022 at 10:09:20AM +0000, Jianbo Liu wrote: > Add more tc police action parameters for flow_offload. They can be used > by driver to check if police can be offloaded. DaveM / Jakub, please ignore this version. We will send v2 with better validation of "ok" action, Cc all relevant maintainers and amend the cover letter to contain the motivation for the patchset (i.e., preparation for more advanced police offload in mlx5). Thanks