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 9109C42FA3; Mon, 31 Jul 2023 14:54:33 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6051040A89; Mon, 31 Jul 2023 14:54:33 +0200 (CEST) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by mails.dpdk.org (Postfix) with ESMTP id C573E4067B for ; Mon, 31 Jul 2023 14:54:31 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id CB1A632008FB; Mon, 31 Jul 2023 08:54:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Mon, 31 Jul 2023 08:54:31 -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=fm3; t= 1690808069; x=1690894469; bh=nstnhi/ennWhg0An+7gPNU5ZoQeAUgQGCV4 No8h5QWo=; b=wL/3hliIRZlT+mqi5o3Swcc7bVzoWWH9rT2EoSOQG5WQ47EZAuW p9PjUOcmEZvkGWI8VMBrtrJuSVv+ozGH8hqpV8wp15KyG07zB7LHjijsyuKVbRiw uTKXGpzvrZlVamjmLKwPnN8QWvN9SS6OfZftv5qCcQq0upuNGhr5lOgCf/ZiUAcQ JPbqdhpbE9VsaIWjmLqrpLv1COKn5zpnigi5NHrffrbIjgYVozibLGGodGqAIT+e wXa0LWmoeikGN6pBV7HiSGq/xg7Nk+FmVJHCYS/YVTL/sDTl4uQMz7/Crjnlru3I PHmy4EIFAvFb53UWl/8IE2e22/nj0oHmOQA== 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=fm3; t= 1690808069; x=1690894469; bh=nstnhi/ennWhg0An+7gPNU5ZoQeAUgQGCV4 No8h5QWo=; b=XhTtoTT81gtmnDJv/DhNrQzlSSIBWQItn2QsSVZIMlEFpLJ5MZL ud51axmz1GSzE0UH9chW/4B8iObCePjLByOKEP6plVtffl4KNJbGvtK3aUYZCgcx B0t3TH9ZJHs4yBP3TAW9EsBip01SMdvekUUhlPB1TW8rG/JUos5GOSv9a7sdVHCE zMV6jKF8QzjjUlq1N8dnbT1OcOEDg4P95uTnxESiuWfhJJ4mFddET9VNkwEjmmpw wLaZjcVe2zFOs/egkXHsWa+8FUebWk3n8hK7izVqNLyLDz1IDgsT30YOPhDIg6t7 KjDiMbbvZ3CpS4Aiww6XhxsjoZtYDraIsRw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrjeeggdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 31 Jul 2023 08:54:26 -0400 (EDT) From: Thomas Monjalon To: jerinj@marvell.com, Nithin Dabilpuram Cc: ferruh.yigit@intel.com, arybchenko@solarflare.com, orika@mellanox.com, cristian.dumitrescu@intel.com, anatoly.burakov@intel.com, John McNamara , Marko Kovacevic , Olivier Matz , dev@dpdk.org, kkanas@marvell.com, Nithin Dabilpuram Subject: Re: [dpdk-dev] [PATCH 1/3] mbuf: add Tx offloads for packet marking Date: Mon, 31 Jul 2023 14:54:25 +0200 Message-ID: <2235168.3ZeAukHxDK@thomas> In-Reply-To: <20200417072254.11455-1-nithind1988@gmail.com> References: <20200417072254.11455-1-nithind1988@gmail.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 Please can you remind what was decided for this feature? I think I should remove it from the roadmap. 17/04/2020 09:22, Nithin Dabilpuram: > From: Nithin Dabilpuram > > Introduce PKT_TX_MARK_IP_DSCP, PKT_TX_MARK_IP_ECN > and PKT_TX_MARK_VLAN_DEI Tx offload flags to support > packet marking. > > When packet marking feature in Traffic manager is enabled, > application has to the use the three new flags to indicate > to PMD on whether packet marking needs to be enabled on the > specific mbuf or not. By setting the three flags, it is > assumed by PMD that application has already verified the > applicability of marking on that specific packet and > PMD need not perform further checks as per RFC. > > Signed-off-by: Krzysztof Kanas > Signed-off-by: Nithin Dabilpuram