From: Dario Faggioli <dario.faggioli@citrix.com>
To: Praveen Kumar <kpraveen.lkml@gmail.com>, xen-devel@lists.xen.org
Cc: george.dunlap@eu.citrix.com
Subject: Re: [PATCH RFC 1/2] xen: credit2: flexible configuration of runqueues
Date: Wed, 22 Mar 2017 15:24:13 +0100 [thread overview]
Message-ID: <1490192653.14782.6.camel@citrix.com> (raw)
In-Reply-To: <1489170396-22611-1-git-send-email-kpraveen.lkml@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1862 bytes --]
Ok, now about the code.
On Fri, 2017-03-10 at 23:56 +0530, Praveen Kumar wrote:
> The user can create runqueue per-cpu using Xen boot parameter like
> below:
>
> credit2_runqueue=cpu
>
> which would mean the following:
> - pCPU 0 belong to runqueue 0
> - pCPU 1 belong to runqueue 1
> - pCPU 2 belong to runqueue 2
> and so on.
>
> Signed-off-by: Praveen Kumar <kpraveen.lkml@gmail.com>
>
> ---
> diff --git a/xen/common/sched_credit2.c b/xen/common/sched_credit2.c
> index af457c1..2bc0013 100644
> --- a/xen/common/sched_credit2.c
> +++ b/xen/common/sched_credit2.c
> @@ -301,6 +301,9 @@ integer_param("credit2_balance_over",
> opt_overload_balance_tolerance);
> * want that to happen basing on topology. At the moment, it is
> possible
> * to choose to arrange runqueues to be:
> *
> + * - per-cpu: meaning that there will be one runqueue per logical
> cpu. This
> + * will happen when if the opt_runqueue parameter is set
> to 'cpu'.
> + *
> * - per-core: meaning that there will be one runqueue per each
> physical
> * core of the host. This will happen if the
> opt_runqueue
> * parameter is set to 'core';
>
This is ok, but you also need to modify the "credit2\_runqueue" section
in docs/misc/xen-command-line.markdown .
In fact, in order to not end up with outdated and incorrect
documentation, we require that the docs are updated in the same patch
that introduces something new (or changes something existing).
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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-22 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 18:26 [PATCH RFC 1/2] xen: credit2: flexible configuration of runqueues Praveen Kumar
2017-03-22 14:17 ` Dario Faggioli
2017-03-22 14:24 ` Dario Faggioli [this message]
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=1490192653.14782.6.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=kpraveen.lkml@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.