From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Anshul Makkar <anshul.makkar@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 00/19] Assorted fixes and improvements to Credit2
Date: Fri, 8 Jul 2016 11:11:15 +0100 [thread overview]
Message-ID: <CAFLBxZYKAdMtnPCXSYXMivzkz691bcNEFkpFbCyo=os7daPuVQ@mail.gmail.com> (raw)
In-Reply-To: <146618450041.23516.9007927860063823148.stgit@Solace.fritz.box>
On Fri, Jun 17, 2016 at 6:32 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> Hi everyone,
>
> Here you go a collection of pseudo-random fixes and improvement to Credit2.
>
> In the process of working on Soft Affinity and Caps support, I stumbled upon
> them, one after the other, and decided to take care.
>
> It's been hard to test and run benchmark, due to the "time goes backwards" bug
> I uncovered [1], and this is at least part of the reason why the code for
> affinity and caps is still missing. I've got it already, but need to refine a
> couple of things, after double checking benchmark results. So, now that we have
> Jan's series [2] (thanks! [*]), and that I managed to indeed run some tests on
> this preliminary set of patches, I decided I better set this first group free,
> while working on finishing the rest.
>
> The various patches do a wide range of different things, so, please, refer to
> Dario Faggioli (19):
I've pushed the following patches:
> xen: sched: make the 'tickled' perf counter clearer
> xen: credit2: insert and tickle don't need a cpu parameter
> xen: credit2: kill useless helper function choose_cpu
> xen: credit2: do not warn if calling burn_credits more than once
> xen: credit2: when tickling, check idle cpus first
> xen: credit2: avoid calling __update_svc_load() multiple times on the same vcpu
> xen: credit2: use non-atomic cpumask and bit operations
The ones below either have outstanding comments, or don't apply
without patches which haven't been applied.
> xen: sched: leave CPUs doing tasklet work alone.
> xen: credit2: read NOW() with the proper runq lock held
> xen: credit2: prevent load balancing to go mad if time goes backwards
> xen: credit2: rework load tracking logic
> tools: tracing: adapt Credit2 load tracking events to new format
> xen: credit2: make the code less experimental
> xen: credit2: add yet some more tracing
> xen: credit2: only marshall trace point arguments if tracing enabled
> tools: tracing: deal with new Credit2 events
> xen: credit2: the private scheduler lock can be an rwlock.
> xen: credit2: implement SMT support independent runq arrangement
> xen: credit2: use cpumask_first instead of cpumask_any when choosing cpu
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-08 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 17:32 [PATCH 00/19] Assorted fixes and improvements to Credit2 Dario Faggioli
2016-06-17 23:08 ` Dario Faggioli
2016-06-20 7:43 ` Jan Beulich
2016-06-20 11:43 ` Dario Faggioli
2016-06-20 11:53 ` Jan Beulich
2016-07-08 10:11 ` George Dunlap [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='CAFLBxZYKAdMtnPCXSYXMivzkz691bcNEFkpFbCyo=os7daPuVQ@mail.gmail.com' \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=anshul.makkar@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@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).