On Thu, Sep 27, 2018 at 11:40:59AM +0100, Anatoly Burakov wrote:
> When we allocate and use DPDK memory, we need to be able to
> differentiate between DPDK hugepage segments and segments that
> were made part of DPDK but are externally allocated. Add such
> a property to memseg lists.
>
> This bre
On 27-Sep-18 12:12 PM, Shreyansh Jain wrote:
On Thursday 27 September 2018 04:38 PM, Burakov, Anatoly wrote:
On 27-Sep-18 12:03 PM, Shreyansh Jain wrote:
On Thursday 27 September 2018 04:10 PM, Anatoly Burakov wrote:
When we allocate and use DPDK memory, we need to be able to
differentiate bet
On Thursday 27 September 2018 04:38 PM, Burakov, Anatoly wrote:
On 27-Sep-18 12:03 PM, Shreyansh Jain wrote:
On Thursday 27 September 2018 04:10 PM, Anatoly Burakov wrote:
When we allocate and use DPDK memory, we need to be able to
differentiate between DPDK hugepage segments and segments that
On 27-Sep-18 12:03 PM, Shreyansh Jain wrote:
On Thursday 27 September 2018 04:10 PM, Anatoly Burakov wrote:
When we allocate and use DPDK memory, we need to be able to
differentiate between DPDK hugepage segments and segments that
were made part of DPDK but are externally allocated. Add such
a p
On Thursday 27 September 2018 04:10 PM, Anatoly Burakov wrote:
When we allocate and use DPDK memory, we need to be able to
differentiate between DPDK hugepage segments and segments that
were made part of DPDK but are externally allocated. Add such
a property to memseg lists.
This breaks the ABI,
When we allocate and use DPDK memory, we need to be able to
differentiate between DPDK hugepage segments and segments that
were made part of DPDK but are externally allocated. Add such
a property to memseg lists.
This breaks the ABI, so bump the EAL library ABI version and
document the change in r
6 matches
Mail list logo
