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 0A48546418; Wed, 19 Mar 2025 05:14:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8CF85402C4; Wed, 19 Mar 2025 05:14:48 +0100 (CET) Received: from fhigh-b3-smtp.messagingengine.com (fhigh-b3-smtp.messagingengine.com [202.12.124.154]) by mails.dpdk.org (Postfix) with ESMTP id F2A824025A for ; Wed, 19 Mar 2025 05:14:45 +0100 (CET) Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfhigh.stl.internal (Postfix) with ESMTP id 20D312540211; Wed, 19 Mar 2025 00:14:45 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Wed, 19 Mar 2025 00:14:45 -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:subject:subject:to:to; s=fm1; t=1742357684; x=1742444084; bh=vdC2MbNdVNSJCAiBWElFaX05z0Q2jf5dVSvCaNEoles=; b= TcKqZ5V3OOu5WIGF4elXpBoVArTzB5LVtpR+DDwEI1vmoUt421GzT5rmFmB4QpYm jgdaUtEb58msNlNe55aMZSnOtqAorSjaxnOG5mWNy5S2X95iNiX2p+rgLpO7EqXV qiMCGTFTseTnl62/ShlJ5aBruiNSe5vPuTAh1FqkOVnpdY8PhlElOKUEIEj7Erwv 96jEoOj7F4D6By26n1UnsT3p2dmqj7RZA3NzK3sNwBEC0owQ72yWVz+zqzS/5wyL gZZetG8BDcNZQGBNB24kqmtYQyx1nJpP67gUI6I8HYX1KAOMlppP6HPLUhOhFv54 R/PJSVWTuxPEUdY3Vxq8ww== 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:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1742357684; x= 1742444084; bh=vdC2MbNdVNSJCAiBWElFaX05z0Q2jf5dVSvCaNEoles=; b=Q x996O0ybYOAjus83cORInfMd56hDxauXSqWz/Gfx6okTiaQtpMwARqE83PD1zgWM a69IFFR4CAArY7xmrRNouVwdgP59D5JxCeHKN6Y6kNz8YISbIWJdTS8+gejDmlnd bCl9MfAzKRdAvrSvHtiLBQsHJST5ocMpfjul5OTSRuF8sbOH4eMdkSnZryf6StSz hic9Amj2EScMB2HnMmDV2imwKC3hNQvxK1Llnqh7t2jbqhmfeLLNQSw4sW2sT237 GmmPA8tRamfQCz4l6tgr4jEeGcfI8/KvbyTgtR/6J+DWLG7HyRA1Ncm373s33MCJ yuVXtgfq4tKiMUQOVBSeg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddugeegfeegucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih gvnhhtshculddquddttddmnecujfgurhephffvvefufffkjghfggfgtgesthfuredttddt jeenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonh hjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeekfeehfedtgedtjeehueeutdfg leefieevkeeikeelkefflefgtdevieehheffudenucffohhmrghinhepughpughkrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthdpnhgspghrtghpthhtohepfedpmhhouggvpe hsmhhtphhouhhtpdhrtghpthhtohepsghruhgtvgdrrhhitghhrghrughsohhnsehinhht vghlrdgtohhmpdhrtghpthhtohepuggvvhesughpughkrdhorhhgpdhrtghpthhtohepkh gvvhhinhdrlhgrrghtiiesihhnthgvlhdrtghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Mar 2025 00:14:44 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: dev@dpdk.org, Kevin Laatz Subject: Re: [PATCH] doc/dmadevs: clarify naming constraints for idxd devices Date: Wed, 19 Mar 2025 05:14:42 +0100 Message-ID: <45228823.doPnVEEUbh@thomas> In-Reply-To: References: <20250131144915.2129736-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 18/02/2025 16:44, Kevin Laatz: > On 31/01/2025 14:49, Bruce Richardson wrote: > > The requirement to have DPDK in the DSA wq name is given in the idxd > > chapter section 5.3.3 [1]. However, that information should also be > > given in section 5.3.1 [2] where we list out the fields to be set and > > what values they should have. > > > > [1]https://doc.dpdk.org/guides-24.11/dmadevs/idxd.html#device-probing-and-initialization > > [2]https://doc.dpdk.org/guides-24.11/dmadevs/idxd.html#intelreg-dsa-devices-using-idxd-kernel-driver > > > > Signed-off-by: Bruce Richardson > > Acked-by: Kevin Laatz Applied, thanks.