[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] atropos still broken?
Hi everyone, This is for Xen 2.0.3. I'm really interested in the functionality of atropos (enforcing CPU partitioning in a non work-conserving fashion). As I had reported earlier, atropos seemed broken in 2.0. It still seems broken now: $ xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 49.1 vm1 1 47 0 -b--- 29.7 9601 $ xm atropos 0 10000 100000 50000 1 $ xm atropos 0 70000 100000 50000 1 Now if I run the slurp program (posted earlier in this list) in vm1, it eats up all the CPU. If I start the same program in dom0 as well, both get ~50% of the CPU. With those parameters, ideally vm1 should be getting 70% and no more, and dom0 should be getting 10% and no more. So it seems atropos is still broken. Is a fix being worked upon? I'd really like to help in any way I can. I'm familiar with the Xen scheduling code; if any of the developers have any idea of where/what the bug is, I'd like to take a crack at it. Thanks, -- Diwaker Gupta http://resolute.ucsd.edu/diwaker ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |