mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Ganapatrao Kulkarni <gpkulkarni@gmail.com>,
	Shanker Donthineni <shankerd@codeaurora.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Vikram Sethi <vikrams@codeaurora.org>,
	Jayachandran C <jnair@caviumnetworks.com>,
	"ganapatrao.kulkarni@cavium.com" <ganapatrao.kulkarni@cavium.com>
Subject: Re: [PATCH] irqchip: gicv3-its: Use NUMA aware memory allocation for ITS tables
Date: Fri, 30 Jun 2017 09:51:40 +0100	[thread overview]
Message-ID: <ab7e26a8-5ab7-7c47-f19c-cb02fbd397b6@arm.com> (raw)
In-Reply-To: <CAFpQJXVh0ojzwqZmT5OgBArx9rpK0_yDw_+gyP8LAkT1e4HWrQ@mail.gmail.com>

On 30/06/17 04:01, Ganapatrao Kulkarni wrote:
> On Fri, Jun 30, 2017 at 8:04 AM, Ganapatrao Kulkarni
> <gpkulkarni@gmail.com> wrote:
>> Hi Shanker,
>>
>> On Sun, Jun 25, 2017 at 9:16 PM, Shanker Donthineni
>> <shankerd@codeaurora.org> wrote:
>>> The NUMA node information is visible to ITS driver but not being used
>>> other than handling errata. This patch allocates the memory for ITS
>>> tables from the corresponding NUMA node using the appropriate NUMA
>>> aware functions.
> 
> IMHO, the description would have been more constructive?
> 
> "All ITS tables are mapped by default to NODE 0 memory.
> Adding changes to allocate memory from respective NUMA NODES of ITS devices.
> This will optimize tables access and avoids unnecessary inter-node traffic."

But more importantly, I'd like to see figures showing the actual benefit
of this per-node allocation. Given that both of you guys have access to
such platforms, please show me the numbers!

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2017-06-30  8:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 15:46 Shanker Donthineni
2017-06-30  2:34 ` Ganapatrao Kulkarni
2017-06-30  3:01   ` Ganapatrao Kulkarni
2017-06-30  8:51     ` Marc Zyngier [this message]
2017-07-03 14:24       ` Shanker Donthineni
2017-07-03 14:53         ` Marc Zyngier
2017-07-03 15:15           ` Shanker Donthineni
2017-07-10  8:48           ` Ganapatrao Kulkarni
2017-07-10  9:06             ` Marc Zyngier
2017-07-10  9:08               ` Ganapatrao Kulkarni
2017-07-10  9:23                 ` Marc Zyngier
2017-07-10 10:21                   ` Ganapatrao Kulkarni
2017-07-10 12:30                     ` Shanker Donthineni
2017-07-10 13:53                       ` Marc Zyngier
2017-07-10 13:50                     ` Marc Zyngier
2017-07-10 14:57                       ` Shanker Donthineni
2017-07-10 15:15                         ` Marc Zyngier
2017-07-11  8:48                           ` Jayachandran C
2017-07-13 15:40                             ` Robert Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab7e26a8-5ab7-7c47-f19c-cb02fbd397b6@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=ganapatrao.kulkarni@cavium.com \
    --cc=gpkulkarni@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=jnair@caviumnetworks.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shankerd@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=vikrams@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®