On Fri, Feb 2, 2018 at 10:53 AM, Christoph Hellwig wrote:
> I've got patches pending to replace all that code with
> dma_direct_alloc, which will do the right thing. They were
> submitted for 4.16, and I will resend them after -rc1.
I see, thanks Christoph !
On Fri, Feb 2, 2018 at 10:53 AM, Christoph Hellwig wrote:
> I've got patches pending to replace all that code with
> dma_direct_alloc, which will do the right thing. They were
> submitted for 4.16, and I will resend them after -rc1.
I see, thanks Christoph !
I've got patches pending to replace all that code with
dma_direct_alloc, which will do the right thing. They were
submitted for 4.16, and I will resend them after -rc1.
I've got patches pending to replace all that code with
dma_direct_alloc, which will do the right thing. They were
submitted for 4.16, and I will resend them after -rc1.
On Wed, 2018-01-31 at 14:45 -0800, Eric Dumazet wrote:
> From: Eric Dumazet
>
> Some devices (like mlx4) try hard to allocate memory on selected
> NUMA node, but it turns out intel_alloc_coherent() is not NUMA
> aware yet.
>
> Note that dma_generic_alloc_coherent() in
On Wed, 2018-01-31 at 14:45 -0800, Eric Dumazet wrote:
> From: Eric Dumazet
>
> Some devices (like mlx4) try hard to allocate memory on selected
> NUMA node, but it turns out intel_alloc_coherent() is not NUMA
> aware yet.
>
> Note that dma_generic_alloc_coherent() in arch/x86/kernel/pci-dma.c
From: Eric Dumazet
Some devices (like mlx4) try hard to allocate memory on selected
NUMA node, but it turns out intel_alloc_coherent() is not NUMA
aware yet.
Note that dma_generic_alloc_coherent() in arch/x86/kernel/pci-dma.c
gets this right.
Signed-off-by: Eric Dumazet
From: Eric Dumazet
Some devices (like mlx4) try hard to allocate memory on selected
NUMA node, but it turns out intel_alloc_coherent() is not NUMA
aware yet.
Note that dma_generic_alloc_coherent() in arch/x86/kernel/pci-dma.c
gets this right.
Signed-off-by: Eric Dumazet
Cc: Benjamin Serebrin
8 matches
Mail list logo