> >> I have added macros to help find the parameters and I have added mempool
> >> functions that allow you to determine if you can use the mempool and
> >> what params it needs. The new mempool functions are mentioned in the
> >> docs for ptr compress.
> >> Please take a look at v11.
> >
> > Gre
On 28/05/2024 20:29, Paul Szczepanek wrote:
>
>
> On 24/05/2024 10:09, Konstantin Ananyev wrote:
>>
>>
>>> I have added macros to help find the parameters and I have added mempool
>>> functions that allow you to determine if you can use the mempool and
>>> what params it needs. The new mempool
On 24/05/2024 10:09, Konstantin Ananyev wrote:
>
>
>> I have added macros to help find the parameters and I have added mempool
>> functions that allow you to determine if you can use the mempool and
>> what params it needs. The new mempool functions are mentioned in the
>> docs for ptr compres
> I have added macros to help find the parameters and I have added mempool
> functions that allow you to determine if you can use the mempool and
> what params it needs. The new mempool functions are mentioned in the
> docs for ptr compress.
> Please take a look at v11.
Great, thanks.
Will try t
I have added macros to help find the parameters and I have added mempool
functions that allow you to determine if you can use the mempool and
what params it needs. The new mempool functions are mentioned in the
docs for ptr compress.
Please take a look at v11.
I did not add a new make pkt buf API
> > From: Paul Szczepanek [mailto:paul.szczepa...@arm.com]
> > Sent: Wednesday, 15 May 2024 19.01
> >
> > On 04/03/2024 14:44, Konstantin Ananyev wrote:
> > >> This feature is targeted for pipeline mode of applications. We see
> > many customers using pipeline mode. This feature helps in reducing
On 15/05/2024 23:34, Morten Brørup wrote:
>> From: Paul Szczepanek [mailto:paul.szczepa...@arm.com]
>>
>> AFAIK DPDK rte_mempool does require the addresses to be virtually
>> contiguous as the memory reservation is done during creation of the
>> mempool and a single memzone is reserved.
>
> No, it
> From: Paul Szczepanek [mailto:paul.szczepa...@arm.com]
> Sent: Wednesday, 15 May 2024 19.01
>
> On 04/03/2024 14:44, Konstantin Ananyev wrote:
> >> This feature is targeted for pipeline mode of applications. We see
> many customers using pipeline mode. This feature helps in reducing
> >> the cos
On 04/03/2024 14:44, Konstantin Ananyev wrote:
>> This feature is targeted for pipeline mode of applications. We see many
>> customers using pipeline mode. This feature helps in reducing
>> the cost of transferring the packets between cores by reducing the copies
>> involved.
>
> I do understand
> On Mar 6, 2024, at 4:31 PM, Paul Szczepanek wrote:
>
> On 02/03/2024 10:33, Morten Brørup wrote:
>> I think that a misconception that arch specific optimizations (such as SIMD
>> code) required stuff to go into EAL has been prevailing, and this
>> misconception is a main reason why EAL has
On 02/03/2024 10:33, Morten Brørup wrote:
I think that a misconception that arch specific optimizations (such as SIMD
code) required stuff to go into EAL has been prevailing, and this misconception
is a main reason why EAL has become so bloated.
Moving features like pointer compression out of E
> > On Mar 1, 2024, at 5:16 AM, Morten Brørup
> > wrote:
> >
> >> From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com]
> >> Sent: Thursday, 22 February 2024 17.16
> >>
> >>> For some reason your email is not visible to me, even though it's in the
> >>> archive.
> >>
> >> No worries.
> From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> Sent: Friday, 1 March 2024 20.57
>
> > On Mar 1, 2024, at 5:16 AM, Morten Brørup
> wrote:
> >
> >> From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com]
> >> Sent: Thursday, 22 February 2024 17.16
> >>
> >>> For some r
> On Mar 1, 2024, at 5:16 AM, Morten Brørup wrote:
>
>> From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com]
>> Sent: Thursday, 22 February 2024 17.16
>>
>>> For some reason your email is not visible to me, even though it's in the
>>> archive.
>>
>> No worries.
>>
>>>
>>> On 02/1
The Community CI Testing Lab had an infra failure this morning and some
patches including yours were affected with false failures. The issue is now
resolved and we are rerunning the tests in question for all patches
submitted today.
On Fri, Mar 1, 2024 at 6:16 AM Morten Brørup
wrote:
> > From: K
> From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com]
> Sent: Thursday, 22 February 2024 17.16
>
> > For some reason your email is not visible to me, even though it's in the
> > archive.
>
> No worries.
>
> >
> > On 02/11/202416:32,Konstantin Ananyev konstantin.v.ananyev wrote:
> >
> For some reason your email is not visible to me, even though it's in the
> archive.
No worries.
>
> On 02/11/202416:32,Konstantin Ananyev konstantin.v.ananyev wrote:
>
> > From one side the code itself is very small and straightforward, > from
> > other side - it is not clear to me what is
For some reason your email is not visible to me, even though it's in the
archive.
On 02/11/202416:32,Konstantin Ananyev konstantin.v.ananyev wrote:
From one side the code itself is very small and straightforward, > from other
side - it is not clear to me what is intended usage for it
within
This patchset is proposing adding a new EAL header with utility functions
that allow compression of arrays of pointers.
When passing caches full of pointers between threads, memory containing
the pointers is copied multiple times which is especially costly between
cores. A compression method will
19 matches
Mail list logo
