xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH v1 2/2] libxl: vcpu-set - allow to decrease vcpu count on overcommitted guests (v2)
Date: Thu, 5 Jun 2014 13:44:10 -0400	[thread overview]
Message-ID: <20140605174409.GC2546@localhost.localdomain> (raw)
In-Reply-To: <1401966177.29759.10.camel@kazak.uk.xensource.com>

On Thu, Jun 05, 2014 at 12:02:57PM +0100, Ian Campbell wrote:
> On Wed, 2014-06-04 at 09:33 -0400, Konrad Rzeszutek Wilk wrote:
> > We have a check to warn the user if they are overcommitting.
> > But the check only checks the hosts CPU amount and does
> > not take into account the case when the user is trying to fix
> > the overcommit. That is - they want to limit the amount of
> > online VCPUs.
> > 
> > This fix allows the user to offline vCPUs without any
> > warnings when they are running an overcommitted guest.
> > 
> > Also while at it, remove crud code.
> > 
> > Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> Contrary to $SUBJECT this is an xl patch not a libxl one. Also there is
> a spurious "(v2)" in the subject.
> 
> > [v2: Remove crud code as spotted by Boris]
> > ---
> >  tools/libxl/xl_cmdimpl.c | 20 +++++++++++++-------
> >  1 file changed, 13 insertions(+), 7 deletions(-)
> > 
> > diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> > index 5195914..5b27bd8 100644
> > --- a/tools/libxl/xl_cmdimpl.c
> > +++ b/tools/libxl/xl_cmdimpl.c
> > @@ -4754,15 +4754,21 @@ static void vcpuset(uint32_t domid, const char* nr_vcpus, int check_host)
> >       * by the host's amount of pCPUs.
> >       */
> >      if (check_host) {
> > +        libxl_dominfo dominfo;
> > +
> >          unsigned int host_cpu = libxl_get_max_cpus(ctx);
> > -        if (max_vcpus > host_cpu) {
> > -            fprintf(stderr, "You are overcommmitting! You have %d physical " \
> > -                    " CPUs and want %d vCPUs! Aborting, use --ignore-host to " \
> > -                    " continue\n", host_cpu, max_vcpus);
> > -            return;
> > +
> > +        if (libxl_domain_info(ctx, &dominfo, domid) != 0)
> > +            dominfo.vcpu_online = host_cpu;
> > +
> > +        if (max_vcpus > dominfo.vcpu_online) {
> > +            if ((max_vcpus > host_cpu)) {
> 
> I think this is 
>         if (max_vcpus > dominfo.vcpu_online && max_vcpus > host_cpu) {
> 
> and if not then the second one has a spurious set of ()s.
> 
> > +                fprintf(stderr, "You are overcommmitting! You have %d physical" \
> 
> You've carried over the typo here (unless you intended to overcommit on
> the number of m's ;-)). Might as well fix while you are here..

Mmmmm.. You are riggggghhhhhhhhhhttttttttt.
> 
> > +                        " CPUs and want %d vCPUs! Aborting, use --ignore-host to" \
> > +                        " continue\n", host_cpu, max_vcpus);
> > +                return;
> > +            }
> >          }
> > -        /* NB: This also limits how many are set in the bitmap */
> > -        max_vcpus = (max_vcpus > host_cpu ? host_cpu : max_vcpus);
> 
> Where did this go?

No need for it actually. As we already do the action if 'max_vcpus >
host_cpu' - which is that we return. So in essence that code will set max_vcpus
to max_vcpus.

> 
> >      }
> >      if (libxl_cpu_bitmap_alloc(ctx, &cpumap, max_vcpus)) {
> >          fprintf(stderr, "libxl_cpu_bitmap_alloc failed\n");
> 
> 

  reply	other threads:[~2014-06-05 17:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:33 [PATCH v1] Misc fixes to libxl (v1) Konrad Rzeszutek Wilk
2014-06-04 13:33 ` [PATCH v1 1/2] libxl: give pciback a chance to do its teardown before we reset the device Konrad Rzeszutek Wilk
2014-06-05 10:58   ` Ian Campbell
2014-06-05 17:41     ` Konrad Rzeszutek Wilk
2014-06-05 17:56       ` Ian Jackson
2014-06-06  9:07         ` Ian Campbell
2014-06-04 13:33 ` [PATCH v1 2/2] libxl: vcpu-set - allow to decrease vcpu count on overcommitted guests (v2) Konrad Rzeszutek Wilk
2014-06-05 11:02   ` Ian Campbell
2014-06-05 17:44     ` Konrad Rzeszutek Wilk [this message]
2014-06-06  9:07       ` Ian Campbell
2015-02-02 20:47         ` Konrad Rzeszutek Wilk
2015-02-02 20:47           ` [PATCH 1/4] libxl: vcpuset: Return error values Konrad Rzeszutek Wilk
2015-02-03 11:29             ` Ian Jackson
2015-02-02 20:47           ` [PATCH 2/4] libxl: vcpuset: Check max_vcpus argument against the maximum number of vCPUs the guest has set Konrad Rzeszutek Wilk
2015-02-03 15:11             ` Ian Jackson
2015-02-03 15:45               ` Konrad Rzeszutek Wilk
2015-03-11 10:56                 ` Ian Campbell
2015-02-02 20:47           ` [PATCH 3/4] libxl: vcpuset: Remove useless limit on max_vcpus Konrad Rzeszutek Wilk
2015-02-02 20:47           ` [PATCH 4/4] libxl: vcpu-set - allow to decrease vcpu count on overcommitted guests (v3) Konrad Rzeszutek Wilk

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=20140605174409.GC2546@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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).