On 4/19/2024 6:23 AM, Chaoyong He wrote:
> Refactor data structure and related logic to make the secondary process
> can work as expect.
>
> ---
> v2:
> * Solve the build problem.
> ---
>
> Chaoyong He (8):
> net/nfp: fix resource leak of secondary process
> net/nfp: fix configuration BAR pro
On 5/21/2024 12:24 PM, Chaoyong He wrote:
>> On 5/21/2024 3:17 AM, Chaoyong He wrote:
On 4/19/2024 6:23 AM, Chaoyong He wrote:
> Refactor data structure and related logic to make the secondary
> process can work as expect.
>
Hi Chaoyong,
Patchset looks good, but
> On 5/21/2024 3:17 AM, Chaoyong He wrote:
> >> On 4/19/2024 6:23 AM, Chaoyong He wrote:
> >>> Refactor data structure and related logic to make the secondary
> >>> process can work as expect.
> >>>
> >>
> >> Hi Chaoyong,
> >>
> >> Patchset looks good, but I have a question related to the motivatio
On 5/21/2024 3:17 AM, Chaoyong He wrote:
>> On 4/19/2024 6:23 AM, Chaoyong He wrote:
>>> Refactor data structure and related logic to make the secondary
>>> process can work as expect.
>>>
>>
>> Hi Chaoyong,
>>
>> Patchset looks good, but I have a question related to the motivation of
>> moving
>>
> On 4/19/2024 6:23 AM, Chaoyong He wrote:
> > Refactor data structure and related logic to make the secondary
> > process can work as expect.
> >
>
> Hi Chaoyong,
>
> Patchset looks good, but I have a question related to the motivation of moving
> so many structs to process private data?
>
> No
On 4/19/2024 6:23 AM, Chaoyong He wrote:
> Refactor data structure and related logic to make the secondary process
> can work as expect.
>
Hi Chaoyong,
Patchset looks good, but I have a question related to the motivation of
moving so many structs to process private data?
Normally ethdev is proc
6 matches
Mail list logo
