On 3/30/2017 2:52 PM, Thomas Monjalon wrote:
> 2017-03-30 18:20, Hemant Agrawal:
>> On 3/30/2017 4:59 PM, Ferruh Yigit wrote:
>>> On 3/28/2017 10:45 AM, Hemant Agrawal wrote:
Hi Olivier,
On 3/27/2017 10:00 PM, Olivier Matz wrote:
> Hi Hemant,
>
> On Fri, 24 Mar 2017 17:42
2017-03-30 18:20, Hemant Agrawal:
> On 3/30/2017 4:59 PM, Ferruh Yigit wrote:
> > On 3/28/2017 10:45 AM, Hemant Agrawal wrote:
> >> Hi Olivier,
> >>
> >> On 3/27/2017 10:00 PM, Olivier Matz wrote:
> >>> Hi Hemant,
> >>>
> >>> On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz
> >>> wrote:
> >>
On 3/30/2017 4:59 PM, Ferruh Yigit wrote:
On 3/28/2017 10:45 AM, Hemant Agrawal wrote:
Hi Olivier,
On 3/27/2017 10:00 PM, Olivier Matz wrote:
Hi Hemant,
On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz wrote:
From high level, I'm still a little puzzled by the amount of references
to mbuf in
On 3/28/2017 10:45 AM, Hemant Agrawal wrote:
> Hi Olivier,
>
> On 3/27/2017 10:00 PM, Olivier Matz wrote:
>> Hi Hemant,
>>
>> On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz
>> wrote:
> From high level, I'm still a little puzzled by the amount of references
> to mbuf in a mempool handle
Hi Olivier,
On 3/27/2017 10:00 PM, Olivier Matz wrote:
Hi Hemant,
On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz wrote:
From high level, I'm still a little puzzled by the amount of references
to mbuf in a mempool handler code, which should theorically handle any
kind of objects.
Is it plan
Hi Hemant,
On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz wrote:
> > > From high level, I'm still a little puzzled by the amount of references
> > > to mbuf in a mempool handler code, which should theorically handle any
> > > kind of objects.
> > >
> > > Is it planned to support other kind of
On Fri, 24 Mar 2017 16:38:04 +, Ferruh Yigit wrote:
> On 3/24/2017 4:31 PM, Olivier Matz wrote:
> > Hi Ferruh,
> >
> > On Fri, 24 Mar 2017 15:59:50 +, Ferruh Yigit
> > wrote:
> >> On 3/24/2017 2:57 PM, Ferruh Yigit wrote:
> >>> On 3/17/2017 12:47 PM, Hemant Agrawal wrote:
>
On 3/24/2017 4:31 PM, Olivier Matz wrote:
> Hi Ferruh,
>
> On Fri, 24 Mar 2017 15:59:50 +, Ferruh Yigit
> wrote:
>> On 3/24/2017 2:57 PM, Ferruh Yigit wrote:
>>> On 3/17/2017 12:47 PM, Hemant Agrawal wrote:
DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
QBMAN ha
Hi Ferruh,
On Fri, 24 Mar 2017 15:59:50 +, Ferruh Yigit wrote:
> On 3/24/2017 2:57 PM, Ferruh Yigit wrote:
> > On 3/17/2017 12:47 PM, Hemant Agrawal wrote:
> >> DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
> >> QBMAN hardware block.
> >> CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_O
On 3/24/2017 2:57 PM, Ferruh Yigit wrote:
> On 3/17/2017 12:47 PM, Hemant Agrawal wrote:
>> DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
>> QBMAN hardware block.
>> CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS is set to 'dpaa2', if the pool
>> is enabled.
>>
>> This memory pool currently
On 3/17/2017 12:47 PM, Hemant Agrawal wrote:
> DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
> QBMAN hardware block.
> CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS is set to 'dpaa2', if the pool
> is enabled.
>
> This memory pool currently supports packet mbuf type blocks only.
>
> Sign
On 3/22/2017 11:39 AM, Jianbo Liu wrote:
Hi Hemant,
The 03/17/2017 18:17, Hemant Agrawal wrote:
DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
QBMAN hardware block.
CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS is set to 'dpaa2', if the pool
is enabled.
This memory pool currently suppo
Hi Hemant,
The 03/17/2017 18:17, Hemant Agrawal wrote:
> DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's
> QBMAN hardware block.
> CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS is set to 'dpaa2', if the pool
> is enabled.
>
> This memory pool currently supports packet mbuf type blocks only.
13 matches
Mail list logo