From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id D91CC45B04;
	Thu, 10 Oct 2024 14:51:53 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id A2015402E8;
	Thu, 10 Oct 2024 14:51:53 +0200 (CEST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com
 (mail-co1nam11on2087.outbound.protection.outlook.com [40.107.220.87])
 by mails.dpdk.org (Postfix) with ESMTP id 06ECC402D8
 for <dev@dpdk.org>; Thu, 10 Oct 2024 14:51:52 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none;
 b=TLFrpLzk6I8gbFfbR6SqtawudgAHLLlOZrCX0Vcb7Yes//EjLsNkTMw2Op0LhiwZqqyTVLBtaoXKepUVq+lvPkG4FYf+Rb5y4RPrqwv631YZuOQ46f73rjXmokzSauEjJunTo+iGNK2029AKA3BHHuUIG3rAxfIbfYYlgP4lkHfX4nLaijue+ORSQ1gwnNUge89KFhAMu3hkLUNvrDAJh744bEOn5f9V1h/sLeuBUnyxZiB4o9plQqc0B3FMxhPdnWWiNoiZs8eHJUW8YttMwwzpHKmvKpCetgAmO3HdwWSN+VIuccBsTsGDwkAmFPPrKtDVuyTWR9t/ZWyuVcnImw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; 
 s=arcselector10001;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=nBHqYtVwzQ358p+Eu9ka7fz+lD33uy3YHou0ENpkGVw=;
 b=in/i0zf2KNAYcyq0q0sbdMI8eG7BBAVnRFoJIKnEDiegWq118lcCEg8eANUSMSo5FedB9hg8vGt5bpXJVHCcjkcXTI+i6jlBL1jZR7egEfd3krt0OYBhlHd7mV2DMQaK+t9gwqcOtEcCyHv1zABnfAQZ/9bBjzDjarE+dmmRHW3qoLPIAjgN2UQkoNQiQegxz26ICTmQT4/4knIvAIsDkkacLJXX3Ne1YzX2X2IaFOeK9bpxD04b6qgomf6QE9DmQVpC+8VA2l73WhEK6UE081c8JFUoSaNlixAY/EiK7FZaPLZVHw7DoSqNaT9hsAHx+H4WlPq9tg9UPE1HEG5rtw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
 smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass
 header.d=amd.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; 
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=nBHqYtVwzQ358p+Eu9ka7fz+lD33uy3YHou0ENpkGVw=;
 b=w9D93JxLzha6R+dtINnKeNkyrpUxjrzs+645KIfcC8WaATeZfLXA8HKz34/gwu1+iuuZyEQ4dwb4l+IzxqnYRGAtiTKnNmK098UuViw5q3X8ks5N0KLkyDu/sL5l6AC18MrOLea5Hye0H4C+HK4Z3vAV4vWYDdpKYbg4KE0C6kU=
Authentication-Results: dkim=none (message not signed)
 header.d=none;dmarc=none action=none header.from=amd.com;
Received: from SJ2PR12MB8830.namprd12.prod.outlook.com (2603:10b6:a03:4d0::9)
 by DM4PR12MB8570.namprd12.prod.outlook.com (2603:10b6:8:18b::14) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8048.18; Thu, 10 Oct
 2024 12:51:47 +0000
Received: from SJ2PR12MB8830.namprd12.prod.outlook.com
 ([fe80::c3eb:df02:eaa9:2055]) by SJ2PR12MB8830.namprd12.prod.outlook.com
 ([fe80::c3eb:df02:eaa9:2055%4]) with mapi id 15.20.8026.020; Thu, 10 Oct 2024
 12:51:47 +0000
Message-ID: <a74961ca-964d-4452-afaf-3979df104966@amd.com>
Date: Thu, 10 Oct 2024 13:51:37 +0100
User-Agent: Mozilla Thunderbird
Subject: Re: [RFC 0/4] ethdev: rework config restore
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
 Konstantin Ananyev <konstantin.ananyev@huawei.com>,
 "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
References: <20240918092201.33772-1-dsosnowski@nvidia.com>
 <13747524-f073-4749-adbd-be1c7681dbcd@amd.com>
 <CH3PR12MB84606439C098D67CFDE0E634A4722@CH3PR12MB8460.namprd12.prod.outlook.com>
 <b02b69a941a9492cbfa65430ed3d64e9@huawei.com>
 <fe6de95a-8e76-4c4a-8b66-0d021a1d3e4e@amd.com>
 <3833d9270fba43af9d17765056911940@huawei.com>
 <8a6f760c-8bc7-46cd-92e0-a8af66114e2d@amd.com>
 <CH3PR12MB8460918E2D36BE4B4CF5B731A47F2@CH3PR12MB8460.namprd12.prod.outlook.com>
 <5ef19db7-f6fe-4a48-8497-e17b33a262b5@amd.com>
 <CH3PR12MB8460ED019BDDFF59B8DE8592A4782@CH3PR12MB8460.namprd12.prod.outlook.com>
Content-Language: en-US
From: Ferruh Yigit <ferruh.yigit@amd.com>
Autocrypt: addr=ferruh.yigit@amd.com; keydata=
 xsFNBGJDD3EBEAC/M7Tk/DfQSmP1K96vyzdhfSBzlCaGtcxNXorq4fALruqVsD3oi0yfyEz9
 4YN8x7py0o9EL8ZdpOX0skc0AMCDAaw033uWhCn0GLMeGRKUbfOAPvL6ecSDvGD7CJIO9j0J
 eZUvasBgPdM/435PEr9DmC6Ggzdzt8IuG4PoLi5jpFSfcqxZFCCxLUDEo/w0nuguk2FTuYJg
 B2zEZ4JTBZrw7hIHiFh8D8hr6YA6a5uTofq1tr+l048lbtdFUl8TR0aIExVzE4Z8qKZlcE+9
 RQaewjK5Al1jLE4sHdmd3GN+IvgDF3D/fLsi25SKJDeGSdeHkOmaX0qGeM4WKIfU6iARRCiQ
 N3AmBIxZ/A7UXBKLaOyZ+/i3sE6Wb53nrO4i8+0K2Qwyh6LjTeiJAIjYKN43ppxz3DaI+QwQ
 vI+uyHr4Gg0Da9EPPz/YyKauSeOZCfCB5gIfICO0j6x0SCl8uQ2nLpjxcZkf0gjcwUzP3h+S
 3x6NfDji9YEij0zczW/dcSpGgZ6vsFpPrtnP9ZXy6J53yp0kJtOJoOlkEFFdU2yCZnCDseum
 CoudmGLZVvS0/DzHDJejq+3kK3FDGktZBOxZIIpal+nFqS7lVgOZc4+huVv3jyhzoAUOEyXA
 XK5j6o7g8STUY+z33QNnHpdLvecMwuzmvqy0jR54yAbZ64mB9QARAQABzSNGZXJydWggWWln
 aXQgPGZlcnJ1aC55aWdpdEBhbWQuY29tPsLBlwQTAQgAQQIbAwULCQgHAgYVCgkICwIEFgID
 AQIeAQIXgAIZARYhBEm7aYjps5XGsPHCElRTPtCKKm/6BQJkdyEEBQkE3meNAAoJEFRTPtCK
 Km/6UdcP/0/kEp49aIUhkRnQfmKmNVpcBEs4NqceNCWTQlaXdEwL1lxf1L49dsF5Jz1yvWi3
 tMtq0Mk1o68mQ7q8iZAzIeLxGQAlievMNE0BzLWPFmuX+ac98ITBqKdnUAn6ig5ezR+jxrAU
 58utUszDl16eMabtCu76sINL5izB8zCWcDEUB4UqM8iBSQZ7/a7TSBVS0jVBldAORg1qfFIs
 cGMPQn/skhy3QqbK3u3Rhc44zRxvzrQJmhY6T1rpeniHSyGOeIYqjpbpnMU5n1VWzQ4NXvAD
 VDkZ4NDw6CpvF4S2h2Ds7w7GKvT6RRTddrl672IaLcaWRiqBNCPm+eKh4q5/XkOXTgUqYBVg
 Ors8uS9EbQC/SAcp9VHF9fB+3nadxZm4CLPe5ZDJnSmgu/ea7xjWQYR8ouo2THxqNZtkercc
 GOxGFxIaLcJIR/XChh9d0LKgc1FfVARTMW8UrPgINVEmVSFmAVSgVfsWIV+NSpG9/e90E4SV
 gMLPABn1YpJ8ca/IwqovctqDDXfxZOvCPOVWTzQe/ut767W+ctGR1kRkxWcz470SycOcY+PW
 VRPJd91Af0GdLFkwzZgNzkd6Gyc9XXcv4lwwqBLhWrBhqPYB0aZXIG1E/cVTiRp4dWpFHAFD
 DcuLldjIw93lCDsIeEDM9rBizGVMWEoeFmqSe7pzGTPXzsFNBGJDD3EBEAC8fBFQHej8qgIG
 CBzoIEd1cZgPIARlIhRudODXoNDbwA+zJMKtOVwol3Hh1qJ2/yZP11nZsqrP4fyUvMxrwhDe
 WBWFVDbWHLnqXMnKuUU1vQMujbzgq/4Rb9wSMW5vBL6YxhZng+h71JgS/9nVtzyaTtsOTrJi
 6nzFSDx6Wbza2jYvL9rlK0yxJcMEiKwZQ/if4KcOesD0rtxomU/iSEv6DATcJbGXP6T93nPl
 90XksijRKAmOwvdu3A8IIlxiSSVRP0lxiHOeR35y6PjHY2usfEDZZOVOfDfhlCVAIBZUZALv
 VmFOVSTYXeKgYa6Ooaf72+cHM3SgJIbYnevJfFv8YQW0MEAJ/IXE7B1Lk+pHNxwU3VBCrKnA
 fd/PTvviesuYRkrRD6qqZnINeu3b2DouVGGt2fVcGA38BujCd3p8i7azoGc7A6cgF7z9ETnr
 ANrbg1/dJyDmkDxOxVrVquTBbxJbDy2HaIe9wyJTEK2Sznpy62DaHVY+gfDQzexBXM10geHC
 IIUhEnOUYVaq65X3ZDjyAQnNDBQ4uMqSHZk8DpJ22X+T+IMzWzWl+VyU4UZXjkLKPvlqPjJk
 1RbKScek5L2GhxHQbPaD76Hx4Jiel0vm2G+4wei8Ay1+0YRFkhySxogU/uQVXHTv63KzQMak
 oIfnN/V2R0ucarsvMBW+gwARAQABwsF8BBgBCAAmAhsMFiEESbtpiOmzlcaw8cISVFM+0Ioq
 b/oFAmR3IPsFCQTeZ44ACgkQVFM+0Ioqb/qINhAAtcor9bevHy22HvJvXX17IOpPSklZJAeQ
 Az43ZEo5kRlJ8mElc2g3RzYCvL/V3fSiIATxIsLq/MDtYhO8AAvklxND/u2zeBd7BkRZTZZX
 W1V1cM3oTvfx3LOhDu4f2ExQzCGdkzbXTRswSJIe1W0qwsDp+YPekbrsKp1maZArGeu+6FuW
 honeosIrWS98QJmscEhP8ooyJkLDCCOgEk+mJ/JBjzcJGuYn6+Iy/ApMw/vqiLGL1UWekcTA
 g18mREHqIR+A3ZvypIufSFB52oIs1zD/uh/MgmL62bY/Cw6M2SxiVxLRsav9TNkF6ZaNQCgn
 GqifliCEMvEuLZRBOZSYH2A/PfwjYW0Ss0Gyfywmb2IA990gcQsXxuCLG7pAbWaeYazoYYEQ
 NYmWatZNMAs68ERI2zvrVxdJ/fBWAllIEd0uQ4P05GtAHPdTIDQYp545+TPV7oyF0LfXcsQs
 SFVZE6igdvkjfYmh+QOrHGZvpWXLTmffVf/AQ81wspzbfxJ7sYM4P8Mg5kKOsaoUdyA/2qVe
 cMh1CLUHXF1GlofpGbe1lj4KUJVse5g3qwV7i9VrseA8c4VIZewdIjkzAhmmbxl+8rM/LKBH
 dZUMTzME5PFCXJIZ83qkZQ795MTe2YScp9dIV7fsS5tpDwIs7BZNVM1l3NAdK+DLHqNxKuyO 8Zk=
Cc: "dev@dpdk.org" <dev@dpdk.org>,
 Bruce Richardson <bruce.richardson@intel.com>
In-Reply-To: <CH3PR12MB8460ED019BDDFF59B8DE8592A4782@CH3PR12MB8460.namprd12.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO4P123CA0451.GBRP123.PROD.OUTLOOK.COM
 (2603:10a6:600:1aa::6) To SJ2PR12MB8830.namprd12.prod.outlook.com
 (2603:10b6:a03:4d0::9)
MIME-Version: 1.0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: SJ2PR12MB8830:EE_|DM4PR12MB8570:EE_
X-MS-Office365-Filtering-Correlation-Id: 725b1494-ac1d-4a47-11ea-08dce92a4d2c
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;ARA:13230040|376014|1800799024|366016;
X-Microsoft-Antispam-Message-Info: =?utf-8?B?UExPM0xJQWlEYUNBRi9IblgrVjd4bnhGY24wQXNGNjBuWWpqQXVZUXNubXJP?=
 =?utf-8?B?MEpISGxjenQ1NXpHdlU0YndMMnFMU21tLzNiSUowOE1YZjZYME1kcC85K1N0?=
 =?utf-8?B?QmxCU1pOcDE3TCswZ1dOSmVBRjJjT1pOUEcxM2VSK0VqMlY3Wk44V3lZOGdL?=
 =?utf-8?B?eG9uUnRSSmdTWWl5R2pUWVVTbFU4UjRYVGxORlhhblFScmZyQXk1SlIvYzZ1?=
 =?utf-8?B?NUhMMnVYd25wNnpnaFlVRXN2NmhiQkhhanpRamxDYnp0dUdDUHBXdzRacGor?=
 =?utf-8?B?ZGhRZ0RyQk9tMGhkWllnYWw0MUw3RWMwNGNqMjdWcGNZdm1FK0ZZS2tyR21U?=
 =?utf-8?B?MlJiNXppdFVNeGE3QkVlRTlra0l0K1VURVIyR0w0YWloSkhidHJLV2poVUZ1?=
 =?utf-8?B?bExTZ3hLT1daUVdtNkJyalRWOXZQcUYyS0hzNmVHUGQ3WHhTaUtWSEVabVN0?=
 =?utf-8?B?WkdkK3pvTlpSRGw5TFlNNmc2NjVYbjNjdG1nblhRc1N4TnhtV2xxTUF0SERX?=
 =?utf-8?B?SXJiRGZ4VDByQll5U1Rlc21OTlQzajZGMzNZRGtINyt5OU9iMEJrTEN6R0pn?=
 =?utf-8?B?UVl0QXBwemljaEcwcysxVkhMSHE1OFRHa01MNkFsSFp5WGVmNDk5VlhXMlUy?=
 =?utf-8?B?V00ycjM3TW5SU0JCaUhiR01kTDdrOWJtRitNb2VxWnRBZ05Eejk5Z2pyVjJZ?=
 =?utf-8?B?MTg3NlJwb1BDY2NSOTF3aThxU1dPeFhIMm5TcVR2K3hCQlIrZVlFaWp1dVk1?=
 =?utf-8?B?bHR0YlZJSTIvYmUwNXlTMktOa2hjWFAxTXZnSWlrYTZ4RjBaWjdjclJqZlZa?=
 =?utf-8?B?ckNUd1JleGpQYWdJWHkybHh2N3RScGlFckkxbGpoa3FlaWdYMlU4UVJTcXFC?=
 =?utf-8?B?N2Ryd2NwMkdleW5xczhLWVArT1dGelhySmRwVm1yN0VibzdnYkFiUWVwa0Ri?=
 =?utf-8?B?UUpIY2pybEVNZlZXVTA4TlNQeHkweEw4VTJBdk83TVd0cVZlZEVaTG14US9D?=
 =?utf-8?B?SC9jdE9EaHlQbDgzYjR1am1wcFR1TWV0QUlPdEFac3pnaEdYdWoxTitMOFQv?=
 =?utf-8?B?MzFJbWZ2S1pWVDBNVEorSlpvMzhaQ0Q5WUlSQWxUT3Frajhnc1p1WlRmMXdr?=
 =?utf-8?B?TVoyZTdlclV0eURIMno3ZUZydWtVdlZ0K2Vrd2w4TTVKZVZwWllua0xoSm05?=
 =?utf-8?B?R3M4dkpLVnhHVk90WkRoV0lORlFCRWtISjAxa25oVHNYdklvVFNpc3RRbEpn?=
 =?utf-8?B?aE9ZWkZOckxrTWFveVRnc3R1QkYyMExjUlk4RWxkS1lHaFlLWHJGSGNoeVlw?=
 =?utf-8?B?cGh5VmNGcjF2bVFjZlhBODdUV2l0OGY0Slo2R1hmeUhXeFJrR08wQ29YU1k0?=
 =?utf-8?B?MGFCdEVwaHN4VG9YRCtGMUYzZ0d2WjByVXJMNnhuWml1bC9YSzBEdjNJTW1P?=
 =?utf-8?B?S0M0dGd5Ym9ydnFsMmJXTmUrODlLZW1NTTByblU2dFdUcktHWXVYcG15UjZr?=
 =?utf-8?B?a2FjWEg3czRRMjhwdVoyNDBaV044NitSY1lkbHlYZmVqdDM3T2QvY21Cd2Vm?=
 =?utf-8?B?TFY0djIwMlo0Tnc3YzVITXFFYW5nNUtIbVVtMXNHUnhtSjBJakYyT3RiYURw?=
 =?utf-8?B?R3RrMFBlOEN6SCtwa2J1VlNLclVPL0Q4ZE5sNmY4ZkVFVDE3MldiYThITW5h?=
 =?utf-8?B?V2luZnZzaGVBZDVRWmlNRTFnT2tRazRISEkzM0xZSnU0L1FYa3p0RmVnPT0=?=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;
 IPV:NLI; SFV:NSPM; H:SJ2PR12MB8830.namprd12.prod.outlook.com; PTR:; CAT:NONE;
 SFS:(13230040)(376014)(1800799024)(366016); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?S01KdFZWN3JucVhVazZaSko4OEIwSzNvQUErYUVpcFdLMTk3N0hBTHFYR0U1?=
 =?utf-8?B?UTF5N1JlOU1xQkdzMGltVUppV1VGc2RKdEdGY09ZVXRyM0l4aFNPSUVINlM5?=
 =?utf-8?B?ZlJuSk84VVBiZTcyRE9kTE81bFRveGFYclhMQURSQ3ROSk1GT1YxdEZJeVRG?=
 =?utf-8?B?Zy9xRzdtZmROcDJvVkg1Q2pxVGppUThJSU5CblV3Wm42eExXQ25Zem0ycFlJ?=
 =?utf-8?B?c2R5VWJQd1RBK3RQT0JoNWM5cm1wcFoxamxuTHVPOTQ5Z0pUbnVwdmM4b2Fm?=
 =?utf-8?B?TFd3YURYMUp6b29JRWNTcTQ3Y0F1NS9SbFY1clY3aE1mZHNrZjZVenRRN1Vi?=
 =?utf-8?B?di9JM3N1MmNob212dlNFYUFoUFV2WHJCNW9NdHgraGpZN0NqQnVUZnV6eWls?=
 =?utf-8?B?REhnSUlrNklTTnVsSFBnNEhINUtLaHJGUnIvR0ZTYk5hcCtFRW9WbUFvWVlP?=
 =?utf-8?B?UTVhM2w1VkRIOVJGOTVaZ2RlQnZDbEx1bXlhalIvaWxvaUpsTENyK3ZwaE5t?=
 =?utf-8?B?RHZCVFI1WlRVWjlQTVRDOEk3Rk5rekxFTjcrMGpEZE5icnBLODZTcG5OaWdJ?=
 =?utf-8?B?MTU2UTVteDlsOHYyRWNkMHU0SHVYQlpudnlMdWIzcUNTKzdXVjVtaEJ4Y0Jy?=
 =?utf-8?B?Rms2OHh4b2dDVEFETzd6UytBMjJKamowK3grRzBKY1RoVENyOWEvMEZXdDJH?=
 =?utf-8?B?aXN2ZmtJTU9IMW5INytydkhFcUcvSUl1L2JpMzNyOHd2blJUM1JJZEYrb01w?=
 =?utf-8?B?YWg5RnJLWHBmQTlYN283QVRiaDhQSVA3SGgzcE0xZUpkZGxNSEE4dGlhUmNF?=
 =?utf-8?B?bjROMnpXdjlhekFZaGE2RWgvOXZLL0o1eWIvNGtRNm8ybG9PSU1SUldLb2J5?=
 =?utf-8?B?WHdrdXIwK1JCS2s0Y2x0SkNoeHlnK3Y5NHQvSkFTdE5Gc0dHNGsxdnA3TmI3?=
 =?utf-8?B?OGpJK0UxaUgyKytWaTIzcVczMnliZS9UdHVxalEvWTUrSUF3dFo3UUxKalBN?=
 =?utf-8?B?OFl0R2R6WmdrWDRFVk5iZmZ4UXQxQlJKSjc5cmgrbjNZV0hmZ1k1VGh1RWt1?=
 =?utf-8?B?cmYzd2toanBHbTg5OSszS0trbE1ta3NOY0cvZnNZWXpBdkNzczkrWTlDNmdY?=
 =?utf-8?B?SkxsVzAzVUtSVUQrcWM2SnpHZ0xtYmo3Q0ljSFhtYlpmVUtDTUZiM1oyTnJl?=
 =?utf-8?B?eXhTUjBOSGpxamtheG40RXM0TUtDVjZUelJpNWp1bm1LZnFITW1HYTd0Wkhr?=
 =?utf-8?B?bWhwMGJncW4rSTJqeERKMnJRRlBTaHFwSzJLRW9JYWVKenRzT2ZXYldzdUVk?=
 =?utf-8?B?a2tHTm4xanB6aXUvUTNoRko3bjl3OHZQeFZMYzI4dFNHT203RVYvZlBpSnJB?=
 =?utf-8?B?SXZUNGlTcFA3WmVrcy9ZbUtXWFdWa2Z6TzBxbU1XdEQ5S0JnNjZLdlBYZ3dP?=
 =?utf-8?B?VVpDSDBIcGN6SCtLVDZiKzdqNzdkM2l2L1hXTlJrV3J5VVdYeGtxSXR6ajVJ?=
 =?utf-8?B?MUpSYmcrSktndW5iekVRQk9TTUt0T2Z4ZVFZNGtlb2ZjTk55MW5jdlhURWZi?=
 =?utf-8?B?T0dhekdhWWJlOVBWMGMrSWx1THJ4UlpVcWZrRHI1QlZSeHRXU1VxT21FMW92?=
 =?utf-8?B?THhuOVRjc0QyaTJqeDk4NzhMTFpoMGFja1FNSUsrVFp6SytsUndDQWlyQ0NH?=
 =?utf-8?B?dzQ2MTU3MXlMOXZZZWZaMzFQMzZ5TW9iT3FCVTZYelRmUndwWVlKZmxTemNZ?=
 =?utf-8?B?cVBzZG1XV1MvQWJXUmo0Q3REa0RYazQwWnRWK3I5TzNSQllqS1ErMFlHMXN0?=
 =?utf-8?B?N1hZMllucFJYUHlKYlNuekkxY2NqaEpmQ25FdUs1d05URXE2aE55bnlHQzkv?=
 =?utf-8?B?cmo0TlZwYkFybHgwMHhMbzFnS0JOWUZ0Uy85amFwYjcwM0F5RnQyZk1HVktv?=
 =?utf-8?B?L3ZhUmNFRWxlM2YwcW5ld2Z0NFJWempJa2hFNFdJNEd4bC8rNldMaUpjNmJT?=
 =?utf-8?B?NTNJczI4bmJzWkFtT3FzTFV1TTdhUFZKelpYTk9RcVB2Y3Irc0JZSFhqWkZT?=
 =?utf-8?B?cUtoK0pFSGIrZUltWmUxeDRmZ0llSVlPck4wYXNsN2ZTVFdQeWdPSDZYWG80?=
 =?utf-8?Q?2qOM3ltNIfJRr57AHjpIYcw8Q?=
X-OriginatorOrg: amd.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 725b1494-ac1d-4a47-11ea-08dce92a4d2c
X-MS-Exchange-CrossTenant-AuthSource: SJ2PR12MB8830.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Oct 2024 12:51:47.3601 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 2jWcImR3Tcm79kmmJFgm4wzfmsaLnjybzODIGJSD89o8nZ3ryVbsm4uNlWx+5ULQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR12MB8570
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

On 10/10/2024 1:08 PM, Dariusz Sosnowski wrote:
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@amd.com>
>> Sent: Thursday, October 10, 2024 01:17
>> To: Dariusz Sosnowski <dsosnowski@nvidia.com>; Konstantin Ananyev
>> <konstantin.ananyev@huawei.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
>> <thomas@monjalon.net>; Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>> Cc: dev@dpdk.org; Bruce Richardson <bruce.richardson@intel.com>
>> Subject: Re: [RFC 0/4] ethdev: rework config restore
>>
>> External email: Use caution opening links or attachments
>>
>>
>> On 10/9/2024 5:18 PM, Dariusz Sosnowski wrote:
>>>> -----Original Message-----
>>>> From: Ferruh Yigit <ferruh.yigit@amd.com>
>>>> Sent: Wednesday, October 9, 2024 03:08
>>>> To: Konstantin Ananyev <konstantin.ananyev@huawei.com>; Dariusz
>>>> Sosnowski <dsosnowski@nvidia.com>; NBU-Contact-Thomas Monjalon
>>>> (EXTERNAL) <thomas@monjalon.net>; Andrew Rybchenko
>>>> <andrew.rybchenko@oktetlabs.ru>
>>>> Cc: dev@dpdk.org; Bruce Richardson <bruce.richardson@intel.com>
>>>> Subject: Re: [RFC 0/4] ethdev: rework config restore
>>>>
>>>> External email: Use caution opening links or attachments
>>>>
>>>>
>>>> On 10/8/2024 6:21 PM, Konstantin Ananyev wrote:
>>>>>
>>>>>
>>>>>>>>>> We have been working on optimizing the latency of calls to
>>>>>>>>>> rte_eth_dev_start(), on ports spawned by mlx5 PMD. Most of the
>>>>>>>>>> work requires changes in the implementation of
>>>>>>>>>> .dev_start() PMD callback, but I also wanted to start a
>>>>>>>>>> discussion regarding configuration restore.
>>>>>>>>>>
>>>>>>>>>> rte_eth_dev_start() does a few things on top of calling
>>>>>>>>>> .dev_start()
>>>> callback:
>>>>>>>>>>
>>>>>>>>>> - Before calling it:
>>>>>>>>>>     - eth_dev_mac_restore() - if device supports
>>>>>>>>>> RTE_ETH_DEV_NOLIVE_MAC_ADDR;
>>>>>>>>>> - After calling it:
>>>>>>>>>>     - eth_dev_mac_restore() - if device does not support
>>>>>>>>> RTE_ETH_DEV_NOLIVE_MAC_ADDR;
>>>>>>>>>>     - restore promiscuous config
>>>>>>>>>>     - restore all multicast config
>>>>>>>>>>
>>>>>>>>>> eth_dev_mac_restore() iterates over all known MAC addresses -
>>>>>>>>>> stored in rte_eth_dev_data.mac_addrs array - and calls
>>>>>>>>>> .mac_addr_set() and .mac_addr_add() callbacks to apply these
>>>>>>>>>> MAC
>>>> addresses.
>>>>>>>>>>
>>>>>>>>>> Promiscuous config restore checks if promiscuous mode is
>>>>>>>>>> enabled or not, and calls .promiscuous_enable() or
>>>>>>>>>> .promiscuous_disable()
>>>> callback.
>>>>>>>>>>
>>>>>>>>>> All multicast config restore checks if all multicast mode is
>>>>>>>>>> enabled or not, and calls .allmulticast_enable() or
>>>>>>>>>> .allmulticast_disable()
>>>> callback.
>>>>>>>>>>
>>>>>>>>>> Callbacks are called directly in all of these cases, to bypass
>>>>>>>>>> the checks for applying the same configuration, which exist in
>>>>>>>>>> relevant
>>>> APIs.
>>>>>>>>>> Checks are bypassed to force drivers to reapply the configuration.
>>>>>>>>>>
>>>>>>>>>> Let's consider what happens in the following sequence of API calls.
>>>>>>>>>>
>>>>>>>>>> 1. rte_eth_dev_configure()
>>>>>>>>>> 2. rte_eth_tx_queue_setup()
>>>>>>>>>> 3. rte_eth_rx_queue_setup()
>>>>>>>>>> 4. rte_eth_promiscuous_enable()
>>>>>>>>>>     - Call dev->dev_ops->promiscuous_enable()
>>>>>>>>>>     - Stores promiscuous state in dev->data->promiscuous 5.
>>>>>>>>>> rte_eth_allmulticast_enable()
>>>>>>>>>>     - Call dev->dev_ops->allmulticast_enable()
>>>>>>>>>>     - Stores allmulticast state in dev->data->allmulticast 6.
>>>>>>>>>> rte_eth_dev_start()
>>>>>>>>>>     - Call dev->dev_ops->dev_start()
>>>>>>>>>>     - Call dev->dev_ops->mac_addr_set() - apply default MAC address
>>>>>>>>>>     - Call dev->dev_ops->promiscuous_enable()
>>>>>>>>>>     - Call dev->dev_ops->allmulticast_enable()
>>>>>>>>>>
>>>>>>>>>> Even though all configuration is available in dev->data after
>>>>>>>>>> step 5, library forces reapplying this configuration in step 6.
>>>>>>>>>>
>>>>>>>>>> In mlx5 PMD case all relevant callbacks require communication
>>>>>>>>>> with the kernel driver, to configure the device (mlx5 PMD must
>>>>>>>>>> create/destroy new kernel flow rules and/or change netdev config).
>>>>>>>>>>
>>>>>>>>>> mlx5 PMD handles applying all configuration in .dev_start(), so
>>>>>>>>>> the following forced callbacks force additional communication
>>>>>>>>>> with the kernel. The
>>>>>>>>> same configuration is applied multiple times.
>>>>>>>>>>
>>>>>>>>>> As an optimization, mlx5 PMD could check if a given
>>>>>>>>>> configuration was applied, but this would duplicate the
>>>>>>>>>> functionality of the library (for example
>>>>>>>>>> rte_eth_promiscuous_enable() does not call the driver if
>>>>>>>>>> dev->data->promiscuous is set).
>>>>>>>>>>
>>>>>>>>>> Question: Since all of the configuration is available before
>>>>>>>>>> .dev_start() callback is called, why ethdev library does not
>>>>>>>>>> expect .dev_start() to
>>>>>>>>> take this configuration into account?
>>>>>>>>>> In other words, why library has to reapply the configuration?
>>>>>>>>>>
>>>>>>>>>> I could not find any particular reason why configuration
>>>>>>>>>> restore exists as part of the process (it was in the initial DPDK commit).
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> My assumption is .dev_stop() cause these values reset in some
>>>>>>>>> devices, so
>>>>>>>>> .dev_start() restores them back.
>>>>>>>>> @Bruce or @Konstantin may remember the history.
>>>>>>>
>>>>>>> Yep, as I remember, at least some Intel PMDs calling hw_reset() ad
>>>>>>> dec_stop() and even dev_start() to make sure that HW is in a clean
>>>>>>> (known)
>>>> state.
>>>>>>>
>>>>>>>>>
>>>>>>>>> But I agree this is device specific behavior, and can be managed
>>>>>>>>> by what device requires.
>>>>>>>
>>>>>>> Probably yes.
>>>>>>>
>>>>>>>>>
>>>>>>>>>> The patches included in this RFC, propose a mechanism which
>>>>>>>>>> would help with managing which drivers rely on forceful configuration
>> restore.
>>>>>>>>>> Drivers could advertise if forceful configuration restore is
>>>>>>>>>> needed through `RTE_ETH_DEV_*_FORCE_RESTORE` device flag. If
>>>>>>>>>> this flag is set, then the driver in question requires ethdev
>>>>>>>>>> to forcefully restore
>>>>>>>>> configuration.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> OK to use flag for it, but not sure about using 'dev_info->dev_flags'
>>>>>>>>> (RTE_ETH_DEV_*) for this, as this flag is shared with user and
>>>>>>>>> this is all dpdk internal.
>>>>>>>>>
>>>>>>>>> What about to have a dedicated flag for it? We can have a
>>>>>>>>> dedicated set of flag values for restore.
>>>>>>>>
>>>>>>>> Agreed. What do you think about the following?
>>>>>>>
>>>>>>> Instead of exposing that, can we probably make it transparent to
>>>>>>> the user and probably ethdev layer too?
>>>>>>>
>>>>>>
>>>>>> +1 to make it transparent to user, but not sure if we can make it
>>>>>> transparent to ethdev layer.
>>>>>
>>>>> Just to be clear:
>>>>> Let say, using example from above:
>>>>>
>>>>>  rte_eth_dev_start()
>>>>>      - Call dev->dev_ops->dev_start()
>>>>>      - Call dev->dev_ops->mac_addr_set() - apply default MAC address
>>>>>      - Call dev->dev_ops->promiscuous_enable()
>>>>>      - Call dev->dev_ops->allmulticast_enable()
>>>>>
>>>>> We probably can introduce ethdev internal function (still visible to
>>>>> PMDs) that would do last 3 steps:
>>>>> ethdev_replay_user_conf(...)
>>>>>      - Call dev->dev_ops->mac_addr_set() - apply default MAC address
>>>>>      - Call dev->dev_ops->promiscuous_enable()
>>>>>      - Call dev->dev_ops->allmulticast_enable()
>>>>>
>>>>> And let PMD itself to decide does it needs to call it at dev_start() or not.
>>>>> So it will become:
>>>>> rte_eth_dev_start()
>>>>>      - Call dev->dev_ops->dev_start()
>>>>>       -Call ethdev_replay_user_conf(.)
>>>>>               - Call dev->dev_ops->mac_addr_set() - apply default MAC address
>>>>>               - Call dev->dev_ops->promiscuous_enable()
>>>>>               -Call dev->dev_ops->allmulticast_enable()
>>>>>
>>>>> For PMDs that do need to restore user provided config And
>>>>> rte_eth_dev_start()
>>>>>      - Call dev->dev_ops->dev_start()
>>>>>
>>>>> For those who do not.
>>>>>
>>>>
>>>> OK, got it what you mean.
>>>> Pushing restore functionality to PMDs works, but this may be doing
>>>> redundant work on each PMD.
>>>>
>>>> Instead Dariusz suggests PMD to provide a flag to ehtdev to what to
>>>> restore and common code in ethdev does the work.
>>>> My below dedicated data struct comment is to have this flag in a new
>>>> struct, overall like following:
>>>>
>>>> rte_eth_dev_start()
>>>>    - Call dev->dev_ops->dev_start()
>>>>    - Call dev->dev_ops->get_restore_flags(ethdev, RTE_ETH_START, &flags)
>>>>    - if (flags & MAC) dev->dev_ops->mac_addr_set()
>>>>    - if (flags & PROMISC) dev->dev_ops->promiscuous_enable()
>>>>    - ...
>>>
>>> Could you please explain what is the benefit of exposing flags through dev_ops
>> callback vs a dedicated flags field in rte_eth_dev_data?
>>> In both solutions:
>>> - config restore is transparent to the user,
>>> - drivers can omit config restore (either by not implementing the
>>> callback or not providing the flags),
>>> - an ABI change is introduced (not a huge concern, at least for 24.11).
>>>
>>> I understand that my initial proposal with "internal_flags" was too
>>> vague, but renaming and splitting this field into:
>>>
>>> - dev_start_restore_flags
>>> - dev_reset_restore_flags
>>> - and so on...
>>>
>>> seems sufficient, at least in my opinion.
>>>
>>
>> Hi Dariusz,
>>
>> Putting flags to rte_eth_dev_data works, and it is easier since there is direct access
>> from rte_eth_dev to rte_eth_dev_data, so you don't need new dev_ops. So this is
>> a valid option.
>>
>> But benefit of new dev_ops is to keep "struct rte_eth_dev_data" clean.
>>
>> "struct rte_eth_dev_data" is integral data structure for ethdev and it is used in
>> multiple locations, mostly related to the datapath and all drivers needs to deal
>> with fields of this struct.
>> Like [rx]_queues, dev_private, dev_conf all important and used a lot.
>>
>> I want to protect "struct rte_eth_dev_data" from noise as much as possible,
>> though what is noise is not always that clear.
>>
>> This restore flag is not critical, and I expect most of the drivers won't care and
>> populate this restore flag at all. That is why to me it is better have dedicated struct
>> for it and only drivers care about restore feature know it.
> 
> I see. Thank you very much for the explanation.
> 
> In this case, it looks like adding this to dev_ops is the way to go.
> 
> So, summarizing it all:
> 
> 1. dev_ops should be extended with a callback with the following signature and enums/flags:
> 
> enum rte_eth_dev_operation op {
> 	RTE_ETH_START,
> 	RTE_ETH_STOP,
> 	RTE_ETH_RESET,
> };
> 
> #define RTE_ETH_RESTORE_MAC_ADDR RTE_BIT32(0)
> #define RTE_ETH_RESTORE_PROMISC RTE_BIT32(1)
> #define RTE_ETH_RESTORE_ALLMULTI RTE_BIT32(2)
> 
> void (*get_restore_flags)(
> 	struct rte_eth_dev *dev,
> 	enum rte_eth_dev_operation op,
> 	uint32_t *flags);
> 
> 2. rte_eth_dev_start() will work as follows:
> 
> - Call dev->dev_ops->dev_start()
> - Call dev->dev_ops->get_restore_flags(dev, RTE_ETH_START, &flags). If callback is not provided, assume flags == 0.
> - if (flags & RTE_ETH_RESTORE_MAC_ADDR) - restore MAC addresses
> - and so on...
> 

All above looks good.

> Also, I would like to add the following:
> 
> 3. Patchset introducing this change should add get_restore_flags() implementation to all drivers, which informs that all config should be restored.
> This would preserve the current behavior.
> Later, this could be refined driver by driver.
> 
> What do you think?
> 

What you are saying is correct, but I suspect most of the drivers don't
really need this restore, but they have it since it was in the ethdev layer.

If we introduce back restore via get_restore_flags(), it may stay as it
is in drivers, at least for most of them.

What do you think to risk breaking stuff for this case.

So don't implement this in the drivers by default, so who needs it will
recognize the issue and will implement it. If we merge this patch for
-rc1, it gives enough time for drivers to detect the issue and fix it.

Only we may implement this to the drivers that exist when this restore
code was introduced.
I mean whatever driver exist in the initial DPDK commit, implement this
logic only to those drivers.

> Also, there's an open question about 'stop' and 'reset' operations.
> At the moment, ethdev layer does not do any config manipulation during these operations.
> Maybe we should limit get_restore_flags() to 'start' only?
> 

Ack, I was about to suggest the same, for now only have 'RTE_ETH_START'
as a placeholder for later possible usages.

>>
>>
>>
>>>>
>>>> So PMDs only will provide what to restore with an internal API and
>>>> common ethdev layer will restore it.
>>>> If no restore required PMD may not implement .get_restore_flags() at all.
>>>>
>>>> Additionally, RTE_ETH_START, RTE_ETH_RESET etc flag can be provided
>>>> to internal API to get what to restore in different states...
>>>>
>>>>>> Suggested 'internal_flag' in "struct rte_eth_dev_data" can be
>>>>>> confusing and open to interpretation what to use it for and by time
>>>>>> become source of defect.
>>>>>
>>>>> Yes, same thoughts.
>>>>>
>>>>>> Instead what do you think to have a separate, dedicated data struct for it?
>>>>>
>>>>> Hmm... not sure I understood you here...
>>>>>
>>>>>>
>>>>>>> Might be we can move this restoration code into the new ethdev
>>>>>>> helper function,(ethdevd_user_config_restore()  or so) that PMD
>>>>>>> can invoke
>>>> during its dev_start() if needed?
>>>>>>>
>>>>>>>>
>>>>>>>> #define RTE_ETH_DEV_INTERNAL_PROMISC_FORCE_RESTORE
>> RTE_BIT32(0)
>>>>>>>> #define RTE_ETH_DEV_INTERNAL_ALLMULTI_FORCE_RESTORE
>> RTE_BIT32(1)
>>>>>>>> #define RTE_ETH_DEV_INTERNAL_MAC_ADDR_FORCE_RESTORE
>>>> RTE_BIT32(2)
>>>>>>>>
>>>>>>>> struct rte_eth_dev_data {
>>>>>>>>    /* snip */
>>>>>>>>
>>>>>>>>    uint32_t dev_flags;
>>>>>>>>
>>>>>>>>    /**
>>>>>>>>     * Internal device capabilities, used only by ethdev library.
>>>>>>>>     * Certain functionalities provided by the library might
>> enabled/disabled,
>>>>>>>>     * based on driver exposing certain capabilities.
>>>>>>>>     */
>>>>>>>>    uint32_t internal_flags;
>>>>>>>>
>>>>>>>>    /* snip */
>>>>>>>> };
>>>>>>>>
>>>>>>>>> Also perhaps we have go into details what needs to be restored
>>>>>>>>> after 'stop' and what needs to be restored after 'reset' and use
>>>>>>>>> similar
>>>> mechanism etc...
>>>>>>>>
>>>>>>>> I think we should look into that.
>>>>>>>> Any 'codification' of semantics between drivers and ethdev
>>>>>>>> library is good in
>>>> my opinion.
>>>>>>>>
>>>>>>>> At least right now, ethdev does not change any configuration in
>>>>>>>> 'stop' and
>>>> 'reset' from what I see.
>>>>>>>> But that's on library side only.
>>>>>>>>
>>>>>>>>>> This way, if we would conclude that it makes sense for
>>>>>>>>>> .dev_start() to handle all starting configuration aspects, we
>>>>>>>>>> could track which drivers still rely
>>>>>>>>> on configuration restore.
>>>>>>>>>>
>>>>>>>>>> Dariusz Sosnowski (4):
>>>>>>>>>>   ethdev: rework config restore
>>>>>>>>>>   ethdev: omit promiscuous config restore if not required
>>>>>>>>>>   ethdev: omit all multicast config restore if not required
>>>>>>>>>>   ethdev: omit MAC address restore if not required
>>>>>>>>>>
>>>>>>>>>>  lib/ethdev/rte_ethdev.c | 39
>>>>>>>>>> ++++++++++++++++++++++++++++++++++-----
>>>>>>>>>>  lib/ethdev/rte_ethdev.h | 18 ++++++++++++++++++
>>>>>>>>>>  2 files changed, 52 insertions(+), 5 deletions(-)
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 2.39.5
>>>>>>>>>>
>>>>>>>
>>>>>
>>>
>