From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0C3FA2253FE; Tue, 15 Jul 2025 23:49:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752623357; cv=none; b=B9xMXuDpPUPcMVg6jS7W74TkN77bGLtn7TKbOKArfjmo7aOx2rZBrAY+9oiYRBtJwJK1bW6T0Pk1zQJ6iyA8oInMznE7CPvIlTNwl+motl/nlXOIhiBF5LiaSLvjoDrRhWo8lq3KIEYytpdaVzPP1bwzT4VG4+fqJ/C+MgYOXlE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1752623357; c=relaxed/simple; bh=rTwjNk2XHUB+TgCQDxch8dh4VWi/8YBRQJzUHMoyxjE=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=nhbYcY1LHVA67MT0pcRXxJaVajA4wB8oih1MUnxuBEY2Vz5IWkydKbWbgk+IIHg4vsPqKj4pCId1WQdyoCCVaUgdzFodZLKQmnzS7MYHITI3MjM1qu25+laa5sg6YjJRxlAAwAarPOZvPSB/85bMDyaS8BqQ/YgXXlATQVtrE/k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=a987uHj8; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="a987uHj8" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D44DCC4CEE3; Tue, 15 Jul 2025 23:49:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1752623354; bh=rTwjNk2XHUB+TgCQDxch8dh4VWi/8YBRQJzUHMoyxjE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=a987uHj8xrtN0EATfTVGQYerXdJF1RaVdYjMsZIxbK/PEW6T0Ow+c2XR4XswiFP+S CFoKSUxO8gxYKMgihEWfKXVMbGHWPZ5aiav1vk+ZP7ua0qN8FLSh6CVucnNjczq46h 1Hg8onNCAtSG9T2XzvWdkUdZ8yC3ljlqiaNuxuBCio4ZXcmFQS3karUEpV0U5MpYTI kgJJZYvOA3OLsYy6toXbm0a5tlRDJvgbJizYR58UVdLQv4rBXolKtoXtMQTSYGASgw sOl8wcRI2QbUKOkxp1TPev2NQIfXx7zPT67NhRj9sbaJXarPSK4BOXq5FuA5+O/DrJ h5mcpUUIzZYeQ== Date: Tue, 15 Jul 2025 16:49:13 -0700 From: Jakub Kicinski To: Song Yoong Siang Cc: "David S . Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , Jonathan Corbet , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , Stanislav Fomichev , netdev@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org Subject: Re: [PATCH bpf-next,v4 1/1] doc: clarify XDP Rx metadata handling and driver requirements Message-ID: <20250715164913.3ed08273@kernel.org> In-Reply-To: <20250715071502.3503440-1-yoong.siang.song@intel.com> References: <20250715071502.3503440-1-yoong.siang.song@intel.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 15 Jul 2025 15:15:02 +0800 Song Yoong Siang wrote: > -An XDP program can store individual metadata items into this ``data_meta`` > +Certain devices may utilize the ``data_meta`` area for specific purposes. Calling headroom "``data_meta`` area" is confusing, IMO. I'd say: Certain devices may prepend metadata to received packets. And the rest of this paragraph can stay as is. > +Drivers for these devices must move any hardware-related metadata out from the > +``data_meta`` area before presenting the frame to the XDP program. This ensures > +that the XDP program can store individual metadata items into this ``data_meta``