Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-02-08 Thread Rahul Gupta
gt; ok...@kernel.org, sujithsan...@microsoft.com, > sowmini.varad...@microsoft.com, krathina...@microsoft.com, > rahulrgupt...@gmail.com > Subject: Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into > sub-functions > User-Agent: Mutt/1.5.21 (2010-09-15) > > On (02/02/

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-02-03 Thread Rahul Gupta
crosoft.com, > ok...@kernel.org, sujithsan...@microsoft.com, > sowmini.varad...@microsoft.com, krathina...@microsoft.com, > rahulrgupt...@gmail.com > Subject: Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into > sub-functions > > 29/01/2024 08:55, David Marchand: > >

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-02-02 Thread Thomas Monjalon
29/01/2024 08:55, David Marchand: > On Mon, Jan 29, 2024 at 6:35 AM Rahul Gupta > wrote: > > > Looking at what this patch does.. I am under the impression all you > > > really need is rte_eal_init without initial probing. > > > Such behavior can probably be achieved with a allowlist set to a non >

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-28 Thread David Marchand
On Mon, Jan 29, 2024 at 6:35 AM Rahul Gupta wrote: > > Looking at what this patch does.. I am under the impression all you > > really need is rte_eal_init without initial probing. > > Such behavior can probably be achieved with a allowlist set to a non > > existing device (like for example "-a 000

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-28 Thread Rahul Gupta
.microsoft.com, ok...@kernel.org, > sujithsan...@microsoft.com, sowmini.varad...@microsoft.com, > krathina...@microsoft.com, rahulrgupt...@gmail.com, Rahul Gupta > > Subject: Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into > sub-functions > > On Wed, Jan 24, 2024 at 2:4

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-24 Thread Tyler Retzlaff
On Wed, Jan 24, 2024 at 05:45:11AM -0800, Rahul Gupta wrote: > From: Rahul Gupta > > In continuation to the following email, I am sending this patch. > (https://inbox.dpdk.org/dev/20231110172523.ga17...@microsoft.com/) > > Initialization requires rte_eal_init + rte_pktmbuf_pool_create which > ca

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-24 Thread David Marchand
On Wed, Jan 24, 2024 at 2:45 PM Rahul Gupta wrote: > > From: Rahul Gupta > > In continuation to the following email, I am sending this patch. > (https://inbox.dpdk.org/dev/20231110172523.ga17...@microsoft.com/) > > Initialization requires rte_eal_init + rte_pktmbuf_pool_create which > can consume

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-24 Thread Stephen Hemminger
On Wed, 24 Jan 2024 05:45:11 -0800 Rahul Gupta wrote: > + * returns current status of execution on a given lcore > + */ > +__rte_experimental int > +rte_eal_init_async_setup_done(int lcore_id) > +{ > + int ret = (lcore_config[lcore_id].state) parenthesis not needed here

Re: [dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-24 Thread Stephen Hemminger
On Wed, 24 Jan 2024 05:45:11 -0800 Rahul Gupta wrote: > + > +/* > + * waits until function executing on given lcore finishes. > + * returns value returned by the function executing on that lcore. > + */ > +__rte_experimental int > +rte_eal_init_wait_async_setup_complete(void) > +{ > + int lco

[dpdk-dev] [PATCH v4] eal: refactor rte_eal_init into sub-functions

2024-01-24 Thread Rahul Gupta
From: Rahul Gupta In continuation to the following email, I am sending this patch. (https://inbox.dpdk.org/dev/20231110172523.ga17...@microsoft.com/) Initialization requires rte_eal_init + rte_pktmbuf_pool_create which can consume a total time of 500-600 ms: a) For many devices FLR may take a si