WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [0/3] DomGrp/SchedGrp Merge RFC

On Jan 31, 2008, at 3:04 PM, Mike D. Day wrote:
I think its worth an attempt to merge the scheduling groups with
domain groups. I'll start looking at some of the ideas I mentioned
above, be happy to work with anyone else who wants to have a go.

Hi Mike,

Here's a rough cut of the domgrps/schedgrps merge. It includes a slightly revised version of domgrps with some enhancements for performance and compatibility with schedgrps. I'd appreciate your feedback to make sure the merged result accurately represents your intent.

DomGrps changes:
- add per-domgrp scheduler-specific data

SchedDom Changes:
- when each domgrp is created, make a csched_dom struct to act as the group representative - when doms join the group, delegate its VCPUs to its representative (instead of a master dom) - removed group management functions, changes to tools, and command line interface

As of right now, when a domain joins a group it must relinquish its VCPU(s) to the group. In the near future I'd like to add the following: - configuration option choose whether a dom will relinquish its VCPUs to the group
- modify xm to show whether members have relinquished their VCPUs
- documentation :)

I haven't done any benchmarks, but on the fast path the extra code should be nearly identical to your original schedgrps implementation, so performance should be the very similar. Other than the merge itself, the practical benefit is that schegrps are now persistent across reboots and host migration (although I haven't tested the latter).

The attached patches should apply cleanly to xen-unstable.hg cs 16975. The intended patch order is: domgrps-vmm.patch, schedgrps.patch, domgrps-tools.patch.

Cheers,
Chris

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel