On 20-Dec-18 5:18 PM, Thomas Monjalon wrote:
20/12/2018 17:16, Stephen Hemminger:
On Thu, 20 Dec 2018 15:32:37 +
Anatoly Burakov wrote:
Currently, the only way to use externally allocated memory
is through rte_malloc API's. While this is fine for a lot
of use cases, it may not be suitable
20/12/2018 17:16, Stephen Hemminger:
> On Thu, 20 Dec 2018 15:32:37 +
> Anatoly Burakov wrote:
>
> > Currently, the only way to use externally allocated memory
> > is through rte_malloc API's. While this is fine for a lot
> > of use cases, it may not be suitable for certain other use
> > case
> Anatoly Burakov (4):
> malloc: separate creating memseg list and malloc heap
> malloc: separate destroying memseg list and heap data
> mem: allow registering external memory areas
> mem: allow usage of non-heap external memory in multiprocess
Applied, thanks
On Thu, 20 Dec 2018 15:32:37 +
Anatoly Burakov wrote:
> Currently, the only way to use externally allocated memory
> is through rte_malloc API's. While this is fine for a lot
> of use cases, it may not be suitable for certain other use
> cases like manual memory management, etc.
>
> This pat
Currently, the only way to use externally allocated memory
is through rte_malloc API's. While this is fine for a lot
of use cases, it may not be suitable for certain other use
cases like manual memory management, etc.
This patchset adds another API to register memory segments
with DPDK (so that AP
5 matches
Mail list logo
