[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] [PATCH RFC v1 4/4] libxc for rt scheduler
- To: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
- From: Meng Xu <xumengpanda@xxxxxxxxx>
- Date: Thu, 17 Jul 2014 18:16:38 -0400
- Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Sisu Xi <xisisu@xxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Dario Faggioli <dario.faggioli@xxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Meng Xu <mengxu@xxxxxxxxxxxxx>, "lichong659@xxxxxxxxx" <lichong659@xxxxxxxxx>, "dgolomb@xxxxxxxxxxxxxx" <dgolomb@xxxxxxxxxxxxxx>
- Delivery-date: Thu, 17 Jul 2014 22:16:57 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
Hi Ian and George,
George Dunlap <George.Dunlap@xxxxxxxxxxxxx>ä2014å7æ17æææååéï
On Thu, Jul 17, 2014 at 4:29 PM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Fri, 2014-07-11 at 16:49 +0200, Dario Faggioli wrote:
>
>> So, the bouncing logic seems fine. Looking at what other schedulers do,
>> there should be no particular need for bouncing anything.
>
> Seems like there is some confusing precedent around the use of sysctl vs
> domctl for sched parameters here.
>
> Most schedulers use domctl but arinc uses sysctl.
They're controlling different things.
domctl is controlling parameters related to *a particular domain* (for
instance, weight or cap); sysctl is relating to setting parameters
*for the scheduler as a whole* (for example, timeslice).
 Do we have to use inline parameters in domctl? Â
Right now, we used the domctl to set/get the parameters of each vcpu of a domain. So from what the functionality does, it should be in domctl. ÂIf we don't have to use inline parameters, I would prefer to use domctl. :-)
The reason why ARINC653 scheduler uses sysctl to set parameters is as George said. It sets the scheduling sequence for the ARINC653 scheduler, instead of setting the parameters of a domain.Â
Thank you very much!
Best,
Meng
Â
--
----------- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|