All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Chong Li <lichong659@gmail.com>
Cc: Chong Li <chong.li@wustl.edu>, Wei Liu <wei.liu2@citrix.com>,
	Sisu Xi <xisisu@gmail.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Ian Campbell <ian.campbell@eu.citrix.com>,
	Meng Xu <mengxu@cis.upenn.edu>,
	Dagaen Golomb <dgolomb@seas.upenn.edu>
Subject: Re: [PATCH v3 for Xen 4.6 3/4] libxl: enable per-VCPU parameter settings for RTDS scheduler
Date: Wed, 8 Jul 2015 16:45:34 +0200	[thread overview]
Message-ID: <1436366734.22672.209.camel@citrix.com> (raw)
In-Reply-To: <CAGHO-iopd+MXeGg_x=c9BVzG7UUBM4SVnKZiC=s6DiPs584NVA@mail.gmail.com>


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

On Wed, 2015-07-08 at 09:35 -0500, Chong Li wrote:
> On Tue, Jul 7, 2015 at 11:23 AM, Dario Faggioli

> >>
> >> +/* Per-VCPU parameters*/
> >> +#define LIBXL_DOMAIN_SCHED_PARAM_VCPU_INDEX_DEFAULT -1
> >> +
> >>  int libxl_domain_sched_params_get(libxl_ctx *ctx, uint32_t domid,
> >>                                    libxl_domain_sched_params *params);
> >>  int libxl_domain_sched_params_set(libxl_ctx *ctx, uint32_t domid,
> >>                                    const libxl_domain_sched_params *params);
> >> +int libxl_vcpu_sched_params_get(libxl_ctx *ctx, uint32_t domid,
> >> +                                  libxl_vcpu_sched_params *params);
> >> +int libxl_vcpu_sched_params_set(libxl_ctx *ctx, uint32_t domid,
> >> +                                  const libxl_vcpu_sched_params *params);
> >>
> > Didn't we say that we wanted the fact that now, at least for RTDS,
> > libxl_domain_sched_params_*() deals with default parameters to be
> > documented in a comment somewhere? Have I missed it?
> 
> I'll implement it in the next version.
> 
> Do both get/set deal with default parameters? I can easily implement
> it in hypervisor, because default parameters
> (RTDS_DEFAULT_PERIOD/BUDGET) are just defined there. But for libxl,
> how do I deal with it without knowing the default values?
>
What I meant was that I am ok with this being implemented in the
hypervisor, but I think we want a comment explaining the difference
between the two sets of operations (the _domain_ one and the _vcpu_ one)
here in the library too.

And in such a comment, it would be good to mention what the _domain_
call does for a scheduler that supports per-vcpu parameters (and the
vice-versa, which, yes, is rather trivial, but still).

The aim would be to give an libxl user an idea of what function he/she
wants, depending on what scheduler and on which parameter, to achieve
its purposes, and what (kind of error/behavior) should be expected if
the wrong one is used.

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:[~2015-07-08 14:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29  2:44 [PATCH v3 for Xen 4.6 0/4] Enable per-VCPU parameter settings for RTDS scheduler Chong Li
2015-06-29  2:44 ` [PATCH v3 for Xen 4.6 1/4] xen: enable " Chong Li
2015-07-07  8:59   ` Jan Beulich
2015-07-07 14:39     ` Dario Faggioli
2015-07-08  6:06       ` Meng Xu
2015-07-08  8:33         ` Dario Faggioli
2015-07-09  1:16           ` Meng Xu
2015-07-10  9:51             ` Dario Faggioli
2015-07-07 14:55     ` Dario Faggioli
2015-07-07 16:09       ` Jan Beulich
2015-07-07 15:33     ` Chong Li
2015-07-07 15:41       ` Jan Beulich
2015-07-07 15:46       ` Dario Faggioli
2015-07-07 14:51   ` Dario Faggioli
2015-06-29  2:44 ` [PATCH v3 for Xen 4.6 2/4] libxc: " Chong Li
2015-06-30 12:22   ` Ian Campbell
2015-06-30 15:18     ` Chong Li
2015-06-30 15:32       ` Ian Campbell
2015-06-30 15:57         ` Chong Li
2015-06-30 16:04           ` Ian Campbell
2015-06-29  2:44 ` [PATCH v3 for Xen 4.6 3/4] libxl: " Chong Li
2015-06-30 12:26   ` Ian Campbell
2015-06-30 15:42     ` Chong Li
2015-06-30 15:57       ` Ian Campbell
2015-06-30 16:10         ` Chong Li
2015-06-30 16:19           ` Ian Campbell
2015-06-30 16:53             ` Chong Li
2015-07-01  0:54             ` Meng Xu
2015-07-01  8:48               ` Ian Campbell
2015-07-01 12:50                 ` Dario Faggioli
2015-07-01 16:59                   ` Chong Li
2015-07-07 16:23   ` Dario Faggioli
2015-07-08 14:35     ` Chong Li
2015-07-08 14:45       ` Dario Faggioli [this message]
2015-06-29  2:44 ` [PATCH v3 for Xen 4.6 4/4] xl: " Chong Li
2015-07-07 15:34   ` Dario Faggioli
2015-07-07 16:01     ` Chong Li
2015-07-07 15:16 ` [PATCH v3 for Xen 4.6 0/4] Enable " Dario Faggioli
2015-07-07 16:11   ` Chong Li

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=1436366734.22672.209.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=chong.li@wustl.edu \
    --cc=dgolomb@seas.upenn.edu \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=lichong659@gmail.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xisisu@gmail.com \
    /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.