On Tue, Mar 24, 2020 at 5:36 PM Andrew Rybchenko
wrote:
>
> On 3/9/20 11:27 AM, Olivier Matz wrote:
> > Hi,
> >
> > On Mon, Mar 09, 2020 at 11:01:25AM +0800, Tonghao Zhang wrote:
> >> On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
> >> wrote:
> >>>
> >>> On 3/7/20 3:51 PM, Andrew Rybchenko wrote
On 3/9/20 11:27 AM, Olivier Matz wrote:
> Hi,
>
> On Mon, Mar 09, 2020 at 11:01:25AM +0800, Tonghao Zhang wrote:
>> On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
>> wrote:
>>>
>>> On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
On 3/6/20 4:37 PM, Jerin Jacob wrote:
> On Fri, Mar 6, 2020 at
Hi Tonghao,
On Mon, Mar 16, 2020 at 03:43:40PM +0800, Tonghao Zhang wrote:
> On Mon, Mar 9, 2020 at 9:15 PM David Marchand
> wrote:
> >
> > On Mon, Mar 9, 2020 at 9:56 AM Tonghao Zhang
> > wrote:
> > > On Mon, Mar 9, 2020 at 4:27 PM Olivier Matz
> > > wrote:
> > > > The fact that the ops ind
On Mon, Mar 9, 2020 at 9:15 PM David Marchand wrote:
>
> On Mon, Mar 9, 2020 at 9:56 AM Tonghao Zhang wrote:
> > On Mon, Mar 9, 2020 at 4:27 PM Olivier Matz wrote:
> > > The fact that the ops index changes during mempool driver lifetime is
> > > indeed frightening, especially knowning that this
On Mon, Mar 9, 2020 at 9:56 AM Tonghao Zhang wrote:
> On Mon, Mar 9, 2020 at 4:27 PM Olivier Matz wrote:
> > The fact that the ops index changes during mempool driver lifetime is
> > indeed frightening, especially knowning that this is a dynamic
> > registration that could happen at any moment in
On Mon, Mar 09, 2020 at 04:55:28PM +0800, Tonghao Zhang wrote:
> On Mon, Mar 9, 2020 at 4:27 PM Olivier Matz wrote:
> >
> > Hi,
> >
> > On Mon, Mar 09, 2020 at 11:01:25AM +0800, Tonghao Zhang wrote:
> > > On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
> > > wrote:
> > > >
> > > > On 3/7/20 3:51
On Mon, Mar 9, 2020 at 4:27 PM Olivier Matz wrote:
>
> Hi,
>
> On Mon, Mar 09, 2020 at 11:01:25AM +0800, Tonghao Zhang wrote:
> > On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
> > wrote:
> > >
> > > On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
> > > > On 3/6/20 4:37 PM, Jerin Jacob wrote:
> > > >
Hi,
On Mon, Mar 09, 2020 at 11:01:25AM +0800, Tonghao Zhang wrote:
> On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
> wrote:
> >
> > On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
> > > On 3/6/20 4:37 PM, Jerin Jacob wrote:
> > >> On Fri, Mar 6, 2020 at 7:06 PM wrote:
> > >>> From: Tonghao Zhang
>
On Sat, Mar 7, 2020 at 8:54 PM Andrew Rybchenko
wrote:
>
> On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
> > On 3/6/20 4:37 PM, Jerin Jacob wrote:
> >> On Fri, Mar 6, 2020 at 7:06 PM wrote:
> >>> From: Tonghao Zhang
> >>>
> >>> The order of mempool initiation affects mempool index in the
> >>> rte_
On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
On 3/6/20 4:37 PM, Jerin Jacob wrote:
On Fri, Mar 6, 2020 at 7:06 PM wrote:
From: Tonghao Zhang
The order of mempool initiation affects mempool index in the
rte_mempool_ops_table. For example, when building APPs with:
$ gcc -lrte_mempool_bucket -lr
On 3/6/20 4:37 PM, Jerin Jacob wrote:
On Fri, Mar 6, 2020 at 7:06 PM wrote:
From: Tonghao Zhang
The order of mempool initiation affects mempool index in the
rte_mempool_ops_table. For example, when building APPs with:
$ gcc -lrte_mempool_bucket -lrte_mempool_ring ...
The "bucket" mempool wi
On Fri, Mar 6, 2020 at 7:06 PM wrote:
>
> From: Tonghao Zhang
>
> The order of mempool initiation affects mempool index in the
> rte_mempool_ops_table. For example, when building APPs with:
>
> $ gcc -lrte_mempool_bucket -lrte_mempool_ring ...
>
> The "bucket" mempool will be registered firstly,
From: Tonghao Zhang
The order of mempool initiation affects mempool index in the
rte_mempool_ops_table. For example, when building APPs with:
$ gcc -lrte_mempool_bucket -lrte_mempool_ring ...
The "bucket" mempool will be registered firstly, and its index
in table is 0 while the index of "ring"
13 matches
Mail list logo