qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: imammedo@redhat.com, david@gibson.dropbear.id.au,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v0] numa: API to lookup NUMA node by address
Date: Mon, 25 May 2015 13:17:57 +0530	[thread overview]
Message-ID: <20150525074757.GE32383@in.ibm.com> (raw)
In-Reply-To: <55546D3A.8010509@redhat.com>

On Thu, May 14, 2015 at 11:39:06AM +0200, Paolo Bonzini wrote:
> 
> 
> On 13/05/2015 20:06, Eduardo Habkost wrote:
> > Also, this introduces a circular dependency between pc-dimm.c and
> > numa.c. Instead of that, pc-dimm could simply notify us when a new
> > device is realized (with just (addr, end, node) as arguments), so we can
> > save the list of memory ranges inside struct node_info.
> > 
> > I wonder if the memory API already provides something that would help
> > us. Paolo, do you see a way we could simply use a MemoryRegion as input
> > to lookup the NUMA node?
> 
> No, but I guess you could add a numa_get/set_memory_region_node_id API
> that uses a hash table.  That's a variant of the "pc-dimm could simply
> notify" numa.c that you propose above.

While you say we can't use MemoryRegion as input to lookup the NUMA node,
you suggest that we add numa_get/set_memory_region_node_id. Does this API
get/set NUMA node id for the given MemoryRegion ? 

Regards,
Bharata.

  reply	other threads:[~2015-05-25  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  7:04 [Qemu-devel] [RFC PATCH v0] numa: API to lookup NUMA node by address Bharata B Rao
2015-05-13 15:33 ` Bharata B Rao
2015-05-13 18:06 ` Eduardo Habkost
2015-05-14  9:39   ` Paolo Bonzini
2015-05-25  7:47     ` Bharata B Rao [this message]
2015-05-25 17:42       ` Eduardo Habkost
2015-06-08  5:58         ` Bharata B Rao
2015-06-08  9:51           ` Igor Mammedov
2015-06-08 15:51             ` Eduardo Habkost
2015-06-08 15:55               ` Paolo Bonzini
2015-06-08 16:09                 ` Eduardo Habkost
2015-06-09  9:23               ` Igor Mammedov
2015-06-09 12:40                 ` Eduardo Habkost
2015-06-10  9:43                   ` Igor Mammedov
2015-06-10 12:14                     ` Eduardo Habkost
2015-06-10 12:50                     ` Bharata B Rao
2015-06-11  6:56                       ` Igor Mammedov
2015-06-11  7:04                         ` Bharata B Rao

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=20150525074757.GE32383@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).