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 542FF42882; Fri, 31 Mar 2023 12:49:55 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D7ADB42D0C; Fri, 31 Mar 2023 12:49:54 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 560FE42D0B for ; Fri, 31 Mar 2023 12:49:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680259793; x=1711795793; h=date:from:to:cc:subject:message-id:references: content-transfer-encoding:in-reply-to:mime-version; bh=b/CGq5wdOiH8ukYQGtQb6HPFx434yqTKI5N5AdEmcsk=; b=V0NxqmzQuwxV/gwy8gtMjRsnvxH1ldghlaSDpZBrbrfmZ3t9f1n1OTPR kbATol85Xtp4s8Z8ykunmcPF/X4S0bE9YG73prquoMhMcXc36wp8KxyLv yqUhe6SrG7gPjpY8wdFkE8NL4Osr9Mx+tWbRxMiDL8i4f01iAP2+L9f3L 6QcoucOJOij5RvDqToP2nqCd5barIlE6GEpS2Oyxg+oyY/O/1tjl1QYZy EPRXsgDWn9lKWsLXTyBmbxsb9fN28ULVCl7AiW3HktguvHMOMZ1YqgCQB i+YcSQGHz/iOX7Z7SY4/ZI7iCMY+Ah0u2KwMdBQK+cKGr8XRCEEBCDyl4 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10665"; a="321074760" X-IronPort-AV: E=Sophos;i="5.98,307,1673942400"; d="scan'208";a="321074760" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Mar 2023 03:49:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10665"; a="662382195" X-IronPort-AV: E=Sophos;i="5.98,307,1673942400"; d="scan'208";a="662382195" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by orsmga006.jf.intel.com with ESMTP; 31 Mar 2023 03:49:51 -0700 Received: from fmsmsx610.amr.corp.intel.com (10.18.126.90) by fmsmsx603.amr.corp.intel.com (10.18.126.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Fri, 31 Mar 2023 03:49:51 -0700 Received: from fmsedg601.ED.cps.intel.com (10.1.192.135) by fmsmsx610.amr.corp.intel.com (10.18.126.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21 via Frontend Transport; Fri, 31 Mar 2023 03:49:51 -0700 Received: from NAM04-BN8-obe.outbound.protection.outlook.com (104.47.74.45) by edgegateway.intel.com (192.55.55.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.21; Fri, 31 Mar 2023 03:49:50 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W+NLwZFMsz5CIGF4gjLNPmKYVScYjURvU/LbAO0vOCdqeO8kYN994IAU7beebO3hrJsRND0ajZc4n9Tr/89r9airn+UjvFa207zNBtmwETNU4KjbwMe6k3QjB2cf7uZIwhUKL2lBWgg3HSSCisbXdf2JRJjaUWMedr1L0J7G/vh2R8of9mG9J0lNXeVjDjlE6ACE/Ino2R1T+nFu8I/gziwf5jqvSE9iQb2AEVB/RPbu+Q24Qdy4J6IQFlqvNnbchPaWVYjAzUsgrjhSOFOseAGz9vlw912HsEvRcCgRuL+hL8F+LyWVlo0EFmEhToMZOBaO6eBHv3fpxaunUPcBbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; 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=SGawyhOatOtdeA2Alkej9V8yqZMJ83T46WQ0CbqgrSk=; b=oNfHfJuQwf75ZlV9Ym42tX+B75DY9wV29wIr1FMtVoGDcjHIaURHukZLlUxCoK+lYBZ57SujnISb+1aNUPKVgTzXeU4j1NmfZICctmYfixhAr+OgWCg8J+q0aN/Emi+3WgPjaF0J0my06JbvDOTscxLy8B5wUz8TXU0/jZb24MCP0xs3YTiCAmA3LBi6a0g+RSEe845B44378//dG4Qz6jabs1GzEO3xcune0xjfBpVMHwNUsRERhKYvcSg3I9j8UMMvWrScltzo6hlqKvdoBAsvdQoeHpd5jghVeiaXfEyXrtn98ACMRHVnGLg/jMmk+TAgeGjYPqdTtVUFBUwaZg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com; Received: from DS0PR11MB7309.namprd11.prod.outlook.com (2603:10b6:8:13e::17) by CY5PR11MB6318.namprd11.prod.outlook.com (2603:10b6:930:3e::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6254.24; Fri, 31 Mar 2023 10:49:49 +0000 Received: from DS0PR11MB7309.namprd11.prod.outlook.com ([fe80::18d0:ac53:aa1d:d19c]) by DS0PR11MB7309.namprd11.prod.outlook.com ([fe80::18d0:ac53:aa1d:d19c%8]) with mapi id 15.20.6222.035; Fri, 31 Mar 2023 10:49:48 +0000 Date: Fri, 31 Mar 2023 11:49:42 +0100 From: Bruce Richardson To: Prashant Upadhyaya CC: Subject: Re: Regarding DPDK API's like rte_timer_subsystem_init/rte_hash_create etc. in VPP Message-ID: References: Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-ClientProxiedBy: LO2P265CA0184.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a::28) To DS0PR11MB7309.namprd11.prod.outlook.com (2603:10b6:8:13e::17) MIME-Version: 1.0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: DS0PR11MB7309:EE_|CY5PR11MB6318:EE_ X-MS-Office365-Filtering-Correlation-Id: 136ec465-c16b-4f90-aa1a-08db31d5a5e9 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: ZN/xOCrMr+fhZvhQ2VAEcpfYf6ewo7C7xS+HwR/dDSTFx7s4sAOzTX11lWt4n+uq60gaXV5zrJUuDMdS5RSG0W9xX2NIuleCQ2i0xFcHUWbPdRL4tVDOfsqrQ1WSLkLNwhD2+pgaU3mSe8uvZWPdoi1At6Dxom2GwdMuhvGoJuvGNjZ52mZuXAH2fQlC/xYrcX4NzezPHns2fNHBnheN8m2JPdeyS8cqXw1ptXBP9JZ50vpDpK7W2YI3Jab6MhRL2Ah2TNdAmMWGnEkzw2Rq1wwIjD0by595OtApaCQfDF/A6g408tiQTm3wpjZS98KyBaYZZCFiqHG51+kciPjoBQBtytjGBlGLs+Ea/Ysd/GicFB5mIw6c0O/3GazIVsWnW8w6fKoL/QBdxGQrFfQiFFiqVhyI1xFkqKie3cMsAJMM1Re6NjvHZix0NSpxuPpUMzr8sJq1wSuw2AIiag/ex3KiJ+CLDsTVAwAjfokOFl4cEH4dEFRu8lnlx7WlIS+B1nA8/Ml9pR5HFDgjcZDThlOoN6PegkLRT/trluYX6I1nwGvVqiJ4ZKoYVJENTiQ9 X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DS0PR11MB7309.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(136003)(366004)(396003)(376002)(346002)(39860400002)(451199021)(186003)(6666004)(6512007)(6486002)(8936002)(53546011)(26005)(6506007)(5660300002)(41300700001)(66946007)(66476007)(8676002)(6916009)(4326008)(66556008)(478600001)(316002)(82960400001)(38100700002)(86362001)(44832011)(83380400001)(2906002); DIR:OUT; SFP:1102; X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1 X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?MHhpelh1cVFJS2tHaUxTVmVKWmVVcXhsRk9kOWk3L0JyNkFqZzI4eUFkdDRs?= =?utf-8?B?ZlUxajI5cTUzZ3lxZTlPeUpUQW1sZzlEcDJlMTZjTkJVbkxXVjc4ZHJkZmJh?= =?utf-8?B?azVNU1lhWnlTalpFcDBYWFZ1WCtjTWE5eGp4SWNGZ2Y1STVRbXoxWlB6UFdK?= =?utf-8?B?L3hicFJYdHllYmEyRDhrbXBmeXRVSzNIcDZGYTJFblVzcFhLc1BVMklWMGpq?= =?utf-8?B?NjZKYm1LK29FVm04KzZrczYyaWJhWkFNdmMwaXVXSVhaVE9DcXplT2RTWEpM?= =?utf-8?B?V1JCbHJaeTJDRXU5U1pMMW9CNmtDR09xT3NqeDJiSWNPNGsySzNEd21admNY?= =?utf-8?B?WDIzYitRVzNpUnVIaktkZTF0S2tqZ3RTTVhyOWtpdmhNcEpmRVh0bDVtSi8x?= =?utf-8?B?UUJRMzhJU2w2Wk8wNUJoWUZLWDU2cHJaVXNDaWVLM00ycFU3U0gvdEVlT3Qz?= =?utf-8?B?TUViTDdkb1FKTm9GaHVVanZ4NlM1RGdLcnlHcDN1THBUOHRFZUppdGxBcUo1?= =?utf-8?B?cjJRbVlwa3ZBTUpzOXRFT0hZQS9peFRQVDIzcHJMZzRMZE52TG1qbysxYXho?= =?utf-8?B?K0s4L2V0cnVOVXhSZzY0Y2RLWnFSaEc2V21ycXFQKzYxc2ZBVk8xR2pGWmFM?= =?utf-8?B?TGlGS0VPQjVFU3JaMmpPOTRzemxOdjdEUU0rZXFRcEtjT2RWRHhhc1dtek51?= =?utf-8?B?cy94ZmdQZHBQT3JyNWFIT1BHWTNtT0lTU0xOejFZZkk5VUJ1cVI3ZlJXRk9J?= =?utf-8?B?TzM0VVNpZm4xV2F6OGE4elhaeGJ4TW5vbzhzdThMUndwV2FYY2dXaTFPeU82?= =?utf-8?B?ZXB5Z1ZlenNuS1hpMHF1TjFLR0dmOFp0emtSMnlrTkVYbUVvanp3ZXpQK2FU?= =?utf-8?B?V0JVU0xzdDZoY205ZmFRVitseWZ3ZW1jaFVjRSt5aVdiV2ZSb1ZqcVlXQ05K?= =?utf-8?B?dHhPQk81dDVOMjVnLys1T2pNanN0N0ZpT3ZhakhtSllETlphUDM5aC9aVlJP?= =?utf-8?B?UlVrcWkxUzg3V0tHd210OEpkVEpaT0o5dzZDbU9sdm9wS01rTlYzQU82T2Y1?= =?utf-8?B?WGlKcm1rRFJ4c2RENUFhQ2hvYVd5OWFKOUNaOEswbDAzdFg3ZjVnQzU5TFRR?= =?utf-8?B?SFJqem1YSVpaQldpZFlWVk1sdG5sWC84SStLSlRIQ1p2WEZ3djN0RnVHeVNu?= =?utf-8?B?RHUyaDZYWFNSN2IwbUsyREt2ZjR3emxtZTVFaVBmTlp6NThKU2w1SzVOdzRu?= =?utf-8?B?WWFSdW1IRGN2eXJZVkM0MGRFQjFzQmJpak1VQVlhdWRrWkFSNXpmTmo2VW5r?= =?utf-8?B?blJ1V2YzZUlFL29hVGh4WnNLU1VuK0lyK3FPLzZBbXhFaDAyNTZXbzhEVFpT?= =?utf-8?B?eS82aDlJcXk0UWlIQTFoSUlGSGJ5NTVCZDJmYkViWlRiUzZiYlhpRFdOc0Nm?= =?utf-8?B?VXVGUmgwVDNxVUFtV29zK1RURUZ0NFcycnBHVWJRUXZBM0N0ZzJzUU5UL1dU?= =?utf-8?B?WVp5TW1zNktHT2VrYXF5bE1BdFVWallpWUNkb1p6Z0d6TUViK1R2Mk9MMlN5?= =?utf-8?B?cGJZMkEvUUlFUVgzU2ZiZlc1VTVhWC9UanBFWWRHQ2RyRzZ2OU1QWDJHQ1lV?= =?utf-8?B?dFVlcDZLRk5MdjMrRkFwQ0lTSnZINUk1dmF1T2xiNVVIZUUwTkNpclV6aE4r?= =?utf-8?B?RXEzYy93b25QNzQ1TkdENUJubnhWY0w4YmNMUHZTMWd3Ty9ibkpOangxSERQ?= =?utf-8?B?L3ZLOEdpUThmRHZOa2pJM1Y3QXViaG9USUw4MzRBT01DQm9ya3JjQURrUlR0?= =?utf-8?B?U2pLbDYxQlNieWcrb2h2Z1AyRkFrT3l5d1NjeGgwUmw1YmpqZzE3dmNSTEVy?= =?utf-8?B?bkkrdC9NU3pMQk9leE5vUkFNZGZEMFpRSGoxOWduZGxXTVN4R1JrNUdNT20v?= =?utf-8?B?dnZNNGMrUnJ6NTFhNDF0NUJkYWliS1h1VE5JVWxIeDJjVWxiOEZJR0lsdlI1?= =?utf-8?B?WnlyZHRtRkNBZWdRczNLSWZzaHBxOVFzSStFS29Rc1ViUDIrbWc2MEtwU3Nz?= =?utf-8?B?Z0U4WG9XQ3BzM0dheDNJak9JT0NRVWZtY2dEeWdiUWdsN2tNbS9qenFWSXhO?= =?utf-8?B?SWR3K0Z2UHdpTE8zb0MwejNzYTVkeFRJSWJmVGMwS0NBZWRnUnlxeVduYThN?= =?utf-8?B?OUE9PQ==?= X-MS-Exchange-CrossTenant-Network-Message-Id: 136ec465-c16b-4f90-aa1a-08db31d5a5e9 X-MS-Exchange-CrossTenant-AuthSource: DS0PR11MB7309.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Mar 2023 10:49:48.6931 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-MailboxType: HOSTED X-MS-Exchange-CrossTenant-UserPrincipalName: 2WFsz/BcvM7n30X9/80/nXSu0KgUZAzXfhPvNaq+0VVEXlBQ8dCDcp/Akiq9mlvTo7r3w+cj6f5EO8qj7g1v21yQBOnk2zyGJDm34N8j+ds= X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY5PR11MB6318 X-OriginatorOrg: intel.com 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 Fri, Mar 31, 2023 at 03:11:18PM +0530, Prashant Upadhyaya wrote: > On Thu, Mar 30, 2023 at 7:34 PM Bruce Richardson > wrote: > > > > On Thu, Mar 30, 2023 at 07:07:23PM +0530, Prashant Upadhyaya wrote: > > > On Thu, Mar 30, 2023 at 6:47 PM Bruce Richardson > > > wrote: > > > > > > > > On Thu, Mar 30, 2023 at 06:42:58PM +0530, Prashant Upadhyaya wrote: > > > > > On Thu, Mar 30, 2023 at 2:50 PM Bruce Richardson > > > > > wrote: > > > > > > > > > > > > On Thu, Mar 30, 2023 at 01:57:52PM +0530, Prashant Upadhyaya wrote: > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > FYI, when replying on list, it's best not to top-post, but put your replies > > > > > > below the email snippet you are replying to. > > > > > > > > > > > > > The hash creation API throws the following error -- > > > > > > > RING: Cannot reserve memory for tailq > > > > > > > HASH: memory allocation failed > > > > > > > > > > > > > > The timer subsystem init api throws this error -- > > > > > > > EAL: memzone_reserve_aligned_thread_unsafe(): Number of requested > > > > > > > memzone segments exceeds RTE_MAX_MEMZONE > > > > > > > > > > > > > > > > > > > Can you try increasing RTE_MAX_MEMZONE. It' defined in DPDK's rte_config.h > > > > > > file, so edit that and then rebuild DPDK. [If you are using the built-in > > > > > > DPDK from VPP, you may need to do a patch for this, add it into the VPP > > > > > > patches direction and then do a VPP rebuild.] > > > > > > > > > > > > Let's see if we can get rid of at least one of the error messages. :-) > > > > > > > > > > > > /Bruce > > > > > > > > > > > > > I did check the code and apparently the memzone and rte zmalloc > > > > > > > related api's are not being able to allocate memory. > > > > > > > > > > > > > > Regards > > > > > > > -Prashant > > > > > > > > > > > > > > On Thu, Mar 30, 2023 at 1:30 PM Bruce Richardson > > > > > > > wrote: > > > > > > > > > > > > > > > > On Thu, Mar 30, 2023 at 10:30:24AM +0530, Prashant Upadhyaya wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > While trying to port some code to VPP (which uses DPDK as the backend > > > > > > > > > driver), I am running into a problem that calls to API's like > > > > > > > > > rte_timer_subsystem_init, rte_hash_create are failing while allocation > > > > > > > > > of memory. > > > > > > > > > > > > > > > > > > This is presumably because VPP inits the EAL with the following arguments -- > > > > > > > > > > > > > > > > > > -in-memory --no-telemetry --file-prefix vpp > > > > > > > > > > > > > > > > > > Is there is something that can be done eg. passing some more parms in > > > > > > > > > the EAL initialization which hopefully wouldn't break VPP but will > > > > > > > > > also be friendly to the RTE timer and hash functions too, that would > > > > > > > > > be great, so requesting some advice here. > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > can you provide some more details on what the errors are that you are > > > > > > > > receiving? Have you been able to dig a little deeper into what might be > > > > > > > > causing the memory failures? The above flags alone are unlikely to cause > > > > > > > > issues with hash or timer libraries, for example. > > > > > > > > > > > > > > > > /Bruce > > > > > > > > > > Thanks Bruce, the error comes from the following function in > > > > > lib/eal/common/eal_common_memzone.c > > > > > memzone_reserve_aligned_thread_unsafe > > > > > > > > > > The condition which spits out the error is the following > > > > > if (arr->count >= arr->len) > > > > > So I printed both of the above values inside this function, and the > > > > > following output came > > > > > > > > > > vpp[14728]: dpdk: EAL init args: --in-memory --no-telemetry --file-prefix vpp > > > > > [New Thread 0x7fffa67b6700 (LWP 14732)] > > > > > count: 0 len: 2560 > > > > > count: 1 len: 2560 > > > > > count: 2 len: 2560 > > > > > [New Thread 0x7fffa5fb5700 (LWP 14733)] > > > > > [New Thread 0x7fffa5db4700 (LWP 14734)] > > > > > count: 3 len: 2560 > > > > > count: 4 len: 2560 > > > > > ### this is the place where I call rte_timer_subsystem_init from my > > > > > code, the above must be coming from any other code from VPP/EAL init, > > > > > the line below is surely because of my call to > > > > > rte_timer_subsystem_init > > > > > count: 0 len: 0 > > > > > > > > > > So as you can see that both values are coming to be zero -- is this > > > > > expected ? I thought the arr->len should have been non zero. > > > > > I must add that the thread which is calling the > > > > > rte_timer_subsystem_init is possibly different than the one which did > > > > > the eal init, do you think that might be a problem... > > > > > I am yet to increase the value of RTE_MAX_MEMZONE, but wanted to share > > > > > the above first for any suggestions. > > > > > > > > > Given the lengths you printed above, increasing the MAX_MEMZONE will not > > > > help things. Is the init call which is failing coming from a non-DPDK > > > > thread? > > > > > > Likely yes, at the moment I am calling it from a CLI which I have added in VPP. > > > Assuming this is the case, do you foresee a problem ? > > > > Could well be a possible cause, yes. With non-DPDK threads, the memory NUMA > > node/socket-id entries could be invalid, and cause the DPDK memory > > allocation to look for memory heaps on non-existent NUMA nodes. > > Can you try using rte_thread_register API in your thread before calling the > > init functions and see if that helps. > > > > /Bruce > > Still no luck ! > I tried two things -- > First, I tried to make the calls from the VPP's fastpath thread (which > I hoped would be a true DPDK thread internally), but the calls failed > like before. > Second, I tried to do a rte_thread_register on this fastpath thread > before making the calls -- this did not help either, same problem. > It appears that VPP's memory management has done something so that > these rte calls are not able to access the expected datastructures at > DPDK level. > It appears I am the only guy in the world trying to make these rte > calls from VPP plugins, I checked on VPP mailing list too and the only > suggestion I got was to replace DPDK memzone/memory allocator > functions with those of VPP. This becomes intricate work as I call rte > timers, hash and rcu functions in my code. > Can I patch DPDK in a generic fashion to reserve memory from a VPP > allocator function or even a malloc at some centralized place or a set > of functions in DPDK ? If doing any such patching, the patches should add new init functions to DPDK to allow init with already-allocated memory, or with a custom memory allocator to allow reserving X amount of memory. That's the only way I can see to do a generic version here. > But the larger question is what are we running into here which is > causing these issues. > It's a very good question. I don't know enough about VPP to answer that - but I suggest you ask on the VPP mailing list, as its likely others in the VPP community may be better able to help. I would suggest doing this before looking into any patching of DPDK, there may be easier workarounds if we know the exact root cause of the issue. Regards, /Bruce