On Tue, Dec 27, 2022 at 10:00 AM zhoumin wrote:
>
> Hi David,
>
>
> First of all, I sincerely apologize for the late reply.
>
> I had checked this issue carefully and had some useful findings.
>
> On Wed, Dec 21, 2022 at 22:57 PM, David Marchand wrote:
> > Hello Min,
> >
> > On Wed, Dec 21, 2022 a
Hi David,
First of all, I sincerely apologize for the late reply.
I had checked this issue carefully and had some useful findings.
On Wed, Dec 21, 2022 at 22:57 PM, David Marchand wrote:
Hello Min,
On Wed, Dec 21, 2022 at 11:49 AM David Marchand
wrote:
Trying to allocate memory on the firs
Hello Min,
On Wed, Dec 21, 2022 at 11:49 AM David Marchand
wrote:
>
> Trying to allocate memory on the first detected numa node has less
> chance to find some memory actually available rather than on the main
> lcore numa node (especially when the DPDK application is started only
> on one numa no
On 12/21/2022 11:16 AM, Bruce Richardson wrote:
> On Wed, Dec 21, 2022 at 11:48:57AM +0100, David Marchand wrote:
>> Trying to allocate memory on the first detected numa node has less
>> chance to find some memory actually available rather than on the main
>> lcore numa node (especially when the DP
On Wed, Dec 21, 2022 at 11:48:57AM +0100, David Marchand wrote:
> Trying to allocate memory on the first detected numa node has less
> chance to find some memory actually available rather than on the main
> lcore numa node (especially when the DPDK application is started only
> on one numa node).
>
Trying to allocate memory on the first detected numa node has less
chance to find some memory actually available rather than on the main
lcore numa node (especially when the DPDK application is started only
on one numa node).
Signed-off-by: David Marchand
---
lib/eal/common/malloc_heap.c | 2 +-
6 matches
Mail list logo
