From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Justin T. Weaver" <jtweaver@hawaii.edu>
Cc: george.dunlap@eu.citrix.com, henric@hawaii.edu, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/2] Credit2: introduce per-vcpu hard and soft affinity
Date: Fri, 2 Jan 2015 17:33:53 +0100 [thread overview]
Message-ID: <1420216433.30581.88.camel@Abyss.station> (raw)
In-Reply-To: <1417307606-2950-1-git-send-email-jtweaver@hawaii.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1541 bytes --]
On Sat, 2014-11-29 at 14:33 -1000, Justin T. Weaver wrote:
> Hello,
>
Hi Justin,
First of all, this is, overall, a really good submission. The only thing
you need to add is a few references.
For example, you already sent something in the past (an RFC, IIRC).
Mention it in the cover letter (I personally also add a link to the
thread).
> I tested this series on a NUMA machine with Dario Faggioli's "fix
> per-socket runqueue setup" patch series applied. Without it, the credit2
> scheduler only creates one run queue, regardless of the type of machine.
>
Yes, I'll resubmit an updated version of that series soon.
So, how did the testing went? Since you're not saying anything, I
imagine that, at least functionally, everything works, at least as far
as you can tell, isn't it so? :-)
At least as far as soft-affinity is concerned, it should not be too
difficult to collect some numbers, to show that it is bringing benefits,
at least for some workloads.
Do you think you'll be able to do something like that?
When doing this same thing for credit1, here's what I did:
http://lists.xen.org/archives/html/xen-devel/2013-02/msg00009.html
https://blog.xenproject.org/2013/03/14/numa-aware-scheduling-development-report/
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
next prev parent reply other threads:[~2015-01-02 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 0:33 [PATCH 0/2] Credit2: introduce per-vcpu hard and soft affinity Justin T. Weaver
2014-11-30 0:33 ` [PATCH 1/2] sched: credit2: respect per-vcpu hard affinity Justin T. Weaver
2015-01-12 18:05 ` Dario Faggioli
2015-01-20 7:21 ` Justin Weaver
2015-02-01 6:51 ` Justin Weaver
2015-02-02 11:12 ` Dario Faggioli
2015-02-02 14:24 ` Dario Faggioli
2015-02-03 9:09 ` Justin Weaver
2015-03-03 3:13 ` Dario Faggioli
2014-11-30 0:33 ` [PATCH 2/2] sched: credit2: consider per-vcpu soft affinity Justin T. Weaver
2015-01-12 18:07 ` Dario Faggioli
2015-01-13 13:06 ` Dario Faggioli
2015-02-11 8:38 ` Justin Weaver
2015-01-02 16:33 ` Dario Faggioli [this message]
2015-01-04 21:32 ` [PATCH 0/2] Credit2: introduce per-vcpu hard and " Justin Weaver
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=1420216433.30581.88.camel@Abyss.station \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=henric@hawaii.edu \
--cc=jtweaver@hawaii.edu \
--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.