Re: [dpdk-dev] [PATCH v5 8/8] mempool: update range info to pool

2017-09-07 Thread Olivier MATZ
On Thu, Sep 07, 2017 at 02:26:49PM +0530, santosh wrote: > > On Thursday 07 September 2017 02:00 PM, Olivier MATZ wrote: > > On Wed, Sep 06, 2017 at 04:58:34PM +0530, Santosh Shukla wrote: > >> HW pool manager e.g. Octeontx SoC demands s/w to program start and end > >> address of pool. Currently,

Re: [dpdk-dev] [PATCH v5 8/8] mempool: update range info to pool

2017-09-07 Thread santosh
On Thursday 07 September 2017 02:00 PM, Olivier MATZ wrote: > On Wed, Sep 06, 2017 at 04:58:34PM +0530, Santosh Shukla wrote: >> HW pool manager e.g. Octeontx SoC demands s/w to program start and end >> address of pool. Currently, there is no such handle in external mempool. >> Introducing rte_mem

Re: [dpdk-dev] [PATCH v5 8/8] mempool: update range info to pool

2017-09-07 Thread Olivier MATZ
On Wed, Sep 06, 2017 at 04:58:34PM +0530, Santosh Shukla wrote: > HW pool manager e.g. Octeontx SoC demands s/w to program start and end > address of pool. Currently, there is no such handle in external mempool. > Introducing rte_mempool_update_range handle which will let HW(pool > manager) to know

[dpdk-dev] [PATCH v5 8/8] mempool: update range info to pool

2017-09-06 Thread Santosh Shukla
HW pool manager e.g. Octeontx SoC demands s/w to program start and end address of pool. Currently, there is no such handle in external mempool. Introducing rte_mempool_update_range handle which will let HW(pool manager) to know when common layer selects hugepage: For each hugepage - update its star