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 A2D1C43D8E; Thu, 11 Apr 2024 15:59:45 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 26354402A8; Thu, 11 Apr 2024 15:59:45 +0200 (CEST) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mails.dpdk.org (Postfix) with ESMTP id 46F424029C for ; Thu, 11 Apr 2024 15:59:43 +0200 (CEST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 1AFC311FB; Thu, 11 Apr 2024 07:00:12 -0700 (PDT) Received: from [192.168.50.86] (usa-sjc-mx-foss1.foss.arm.com [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B58853F64C; Thu, 11 Apr 2024 06:59:41 -0700 (PDT) Message-ID: Date: Thu, 11 Apr 2024 14:59:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 6/6] dts: add statefulness to TestPmdShell Content-Language: en-GB To: =?UTF-8?Q?Juraj_Linke=C5=A1?= Cc: Jeremy Spewock , dev@dpdk.org, Jack Bond-Preston , Honnappa Nagarahalli References: <20240326190422.577028-1-luca.vizzarro@arm.com> <20240326190422.577028-7-luca.vizzarro@arm.com> <1db1b2b8-fac0-41ad-9ba2-911365385a9b@arm.com> <5d35012d-0ffd-4c23-ad0c-8315453b8c9e@arm.com> From: Luca Vizzarro In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 11/04/2024 13:13, Juraj Linkeš wrote: > The changes we discuss below don't seem that big. What do you think, > do we just add another patch to the series? Sure thing, I can take this and add it to v2. > I thought about this a bit as well, it's a good approach. The current > design is top-down, as you say, in that "I have a node and I do things > with the node, including starting testpmd on the node". But it could > also be "I have a node, but I also have other non-node resources at my > disposal and it's up to me how I utilize those". If we can make the > imports work then this is likely the best option. > > > > +1 for simplification. > > > > Let's try shells ingesting nodes if the imports work out then. If not, > we can fall back to dedicated node methods. Sounds good!