From: Dario Faggioli <dario.faggioli@citrix.com>
To: "dunlapg@umich.edu" <dunlapg@umich.edu>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
"uma.sharma523@gmail.com" <uma.sharma523@gmail.com>
Subject: Re: [Patch 2/2]xen/sched_credit2.c : Runqueue per core
Date: Mon, 9 Mar 2015 13:03:42 +0000 [thread overview]
Message-ID: <1425906220.2729.40.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZZgiMQOzc0ROmOTe6qGOEaGk0YcLwtWwph3Fq_S=b5-nQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]
On Mon, 2015-03-09 at 12:18 +0000, George Dunlap wrote:
> On Mon, Mar 9, 2015 at 8:55 AM, Uma Sharma <uma.sharma523@gmail.com> wrote:
> > --- a/xen/common/sched_credit2.c
> > +++ b/xen/common/sched_credit2.c
> > @@ -1935,15 +1938,36 @@ static void init_pcpu(const struct scheduler *ops, int cpu)
> > return;
> > }
> >
> > + /*Figure out which type of runqueue are to be created */
> > + if (!strcmp(opt_credit2_runquque, "socket")) {
> > + rq = 's';
> > + } else if (!strcmp(opt_credit2_runquque, "core")) {
> > + rq = 'c';
> > + } else {
> > + rq = 's';
> > + }
>
> It would be more typical, rather than have this be a char resolving to
> 's' and 'c', to have it be an int, and have the values be #defines;
> for example, "CREDIT2_OPT_RUNQUEUE_CORE" and
> "CREDIT2_OPT_RUNQUEUE_SOCKET".
>
I was about to suggest the same.
> Also, given that your experiments show 'core' to work quite a bit
> better than 'socket', I'd suggest making it default to core rather
> than socket. :-)
>
+1.
Of course, as I said already, you should explain and provide the numbers
about this performance improvement in the cover letter of the series
and, IMO, reference that in the changelog of this patch too (not putting
the full results, but a quick summary of them would be good).
Regards,
Dario
[-- 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
next prev parent reply other threads:[~2015-03-09 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:55 [Patch 2/2]xen/sched_credit2.c : Runqueue per core Uma Sharma
2015-03-09 11:48 ` Jan Beulich
2015-03-09 12:18 ` George Dunlap
2015-03-09 13:03 ` Dario Faggioli [this message]
2015-03-09 13:09 ` Uma Sharma
2015-03-11 18:06 ` Uma Sharma
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=1425906220.2729.40.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=dunlapg@umich.edu \
--cc=uma.sharma523@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.