com;
> robert.rich...@cavium.com; Guohanjun (Hanjun Guo)
> ; John Garry ;
> linux-arm-ker...@lists.infradead.org; Linuxarm
> Subject: Re: [PATCH v3] irqchip: gicv3-its: Use NUMA aware memory allocation
> for ITS tables
>
[...]
> > drivers/irqchip/irq-gic-v3-its.c | 20 +++
Hi Shameer,
On 13/12/2018 10:59, Shameer Kolothum wrote:
From: Shanker Donthineni
The NUMA node information is visible to ITS driver but not being used
other than handling hardware errata. ITS/GICR hardware accesses to the
local NUMA node is usually quicker than the remote NUMA node. How slow
On 11/01/2019 03:53, Ganapatrao Kulkarni wrote:
> Hi Shameer,
>
> Patch looks OK to me, please feel free to add,
> Reviewed-by: Ganapatrao Kulkarni
>
> On Thu, Dec 13, 2018 at 5:25 PM Marc Zyngier wrote:
>>
>> On 13/12/2018 10:59, Shameer Kolothum wrote:
>>> From: Shanker Donthineni
>>>
>>>
Hi Shameer,
Patch looks OK to me, please feel free to add,
Reviewed-by: Ganapatrao Kulkarni
On Thu, Dec 13, 2018 at 5:25 PM Marc Zyngier wrote:
>
> On 13/12/2018 10:59, Shameer Kolothum wrote:
> > From: Shanker Donthineni
> >
> > The NUMA node information is visible to ITS driver but not
On 13/12/2018 10:59, Shameer Kolothum wrote:
> From: Shanker Donthineni
>
> The NUMA node information is visible to ITS driver but not being used
> other than handling hardware errata. ITS/GICR hardware accesses to the
> local NUMA node is usually quicker than the remote NUMA node. How slow
>
From: Shanker Donthineni
The NUMA node information is visible to ITS driver but not being used
other than handling hardware errata. ITS/GICR hardware accesses to the
local NUMA node is usually quicker than the remote NUMA node. How slow
the remote NUMA accesses are depends on the implementation
6 matches
Mail list logo
