All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com, lccycc123@gmail.com,
	george.dunlap@eu.citrix.com, msw@linux.com,
	stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH RESEND v7 1/9] xen: vnuma topology and subop hypercalls
Date: Fri, 22 Aug 2014 15:54:17 +0200	[thread overview]
Message-ID: <1408715657.3725.182.camel@Solace.lan> (raw)
In-Reply-To: <53F75EF7020000780002CB7E@mail.emea.novell.com>


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

On ven, 2014-08-22 at 14:17 +0100, Jan Beulich wrote:

> > +    if ( ret )
> > +        return ret;
> > +
> > +    ret = -EFAULT;
> > +
> > +    if ( copy_from_guest(v->vdistance, u_vnuma->vdistance,
> > +                         nr_vnodes * nr_vnodes) )
> > +        goto vnuma_fail;
> > +
> > +    if ( copy_from_guest(v->vmemrange, u_vnuma->vmemrange, nr_vnodes) )
> > +        goto vnuma_fail;
> 
> Isn't a single memory range per vnode rather limiting? Physical
> machines frequently have at least one node with two ranges to
> accommodate the hole below 4Gb. And since the interface is for
> all guest kinds I'm afraid this will harm setting up guests rather
> sooner than later. (I'm sorry for thinking of this only now.)
> 
This actually was one concern of mine too, during the early stage of
Elena's work. I clearly remember wondering, and even asking, considering
that Linux uses more ranges per node, why using only one was ok for us.

Unfortunately, I OTOH forgot how that discussion ended and how we got to
this point, without me or anyone else (continuing to) complaining... So,
sorry from me too. :-(

Let's see what Elena and others think and, after that, how big of a
piece of work is to introduce support for more than one ranges (or
re-introduce, as I also think I remember this to be some kind of list,
during early versions of the series).

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: 181 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:[~2014-08-22 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  5:08 [PATCH RESEND v7 0/9] vnuma introduction Elena Ufimtseva
2014-08-21  5:08 ` [PATCH RESEND v7 1/9] xen: vnuma topology and subop hypercalls Elena Ufimtseva
2014-08-22 13:17   ` Jan Beulich
2014-08-22 13:54     ` Dario Faggioli [this message]
2014-08-22 17:38       ` Elena Ufimtseva
2014-08-23  4:51         ` Elena Ufimtseva
2014-08-21  5:38 ` [PATCH RESEND v7 0/9] vnuma introduction Elena Ufimtseva
2014-08-21 14:00   ` Dario Faggioli
2014-08-21 14:11     ` Elena Ufimtseva
2014-08-21 14:15       ` 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=1408715657.3725.182.camel@Solace.lan \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.