From: gavin <gbtux@126.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A question on the credit scheduler
Date: Tue, 20 Dec 2011 23:49:49 +0800 (CST) [thread overview]
Message-ID: <e7877fd.3f198.1345c2a185c.Coremail.gbtux@126.com> (raw)
In-Reply-To: <CAFLBxZZP=K504L86WDJ-F+9SuTf7aKU_C=i8nLZwqDuejoVGag@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]
Hi George,
I have another question about the credit2 scheduling.
In a shared cache multi-core system, such as two processors (processor 0 and processor 1), there are two CPU cores in each processor. It seems that the credit scheduling treat all the four cores the same and doesn't distinguish them.
However, I am not sure whether the credit2 scheduling distinguishs them from each other? Maybe the four cores can be divided into two groups. The two cores on the same processor are in the same group. I noted there is development of CPU topology in the To-do list on the credit2 Xen wiki page, but there is no details about the current situation of credit2 scheduling.
--
Best Regards,
Gavin
[-- Attachment #1.2: Type: text/html, Size: 987 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-12-20 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 7:55 A question on the credit scheduler zhikai
2011-12-16 11:04 ` George Dunlap
2011-12-16 14:44 ` gavin
2011-12-16 15:58 ` George Dunlap
2011-12-17 9:16 ` gavin
2011-12-19 10:37 ` George Dunlap
2011-12-19 16:13 ` Shriram Rajagopalan
2011-12-20 7:30 ` gavin
2011-12-20 15:49 ` gavin [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=e7877fd.3f198.1345c2a185c.Coremail.gbtux@126.com \
--to=gbtux@126.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.