xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: keir@xen.org, JBeulich@suse.com, lccycc123@gmail.com,
	george.dunlap@eu.citrix.com, msw@linux.com,
	stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org,
	Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH v2 1/7] xen: vNUMA support for guests.
Date: Thu, 14 Nov 2013 13:11:17 +0100	[thread overview]
Message-ID: <1384431077.29902.138.camel@Abyss> (raw)
In-Reply-To: <5284B872.1090808@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1321 bytes --]

On gio, 2013-11-14 at 11:48 +0000, David Vrabel wrote:
> On 14/11/13 03:26, Elena Ufimtseva wrote:
> > +/* 
> > + * Memory ranges can be used to define
> > + * vNUMA memory node boundaries by the 
> > + * linked list. As of now, only one range
> > + * per domain is suported.
> > + */
> > +
> > +struct vmemrange {
> > +    uint64_t start, end;
> > +    struct vmemrange *next;
> 
> I think this probably wants to be an index into the vmemrange array in
> struct vnuma_topology_info.  It certainly cannot be a bare pointer like
> this.
> 
I think Elena is aiming at a liked list, and so there really is no such
thing as a vmemrange array. This is (probably) because right now only
one memory range is supported, and thus it sounds a bit too much to have
an array there already (e.g., how big?), but at the same time she wanted
to be sure to leave room for future extensions (namely, multiple memory
ranges in each node).

So, if we can ask, with that in mind, what do you think the best ABI
would be?

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-11-14 12:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14  3:26 [PATCH v2 1/7] xen: vNUMA support for guests Elena Ufimtseva
2013-11-14 11:18 ` Dario Faggioli
2013-11-14 21:43   ` George Dunlap
2013-11-15  8:28   ` Jan Beulich
2013-11-14 11:48 ` David Vrabel
2013-11-14 12:11   ` Dario Faggioli [this message]
2013-11-14 14:09     ` Elena Ufimtseva
2013-11-14 21:59 ` George Dunlap
2013-11-14 22:51   ` Elena Ufimtseva
2013-11-14 23:51     ` George Dunlap
2013-11-15  8:50 ` Jan Beulich
2013-11-15 14:14   ` Elena Ufimtseva

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=1384431077.29902.138.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=lccycc123@gmail.com \
    --cc=msw@linux.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=ufimtseva@gmail.com \
    --cc=xen-devel@lists.xen.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).