|| ||Paul Turner <firstname.lastname@example.org> |
|| ||email@example.com |
|| ||[patch 00/15] CFS Bandwidth Control V6 |
|| ||Tue, 03 May 2011 02:28:46 -0700|
|| ||Peter Zijlstra <firstname.lastname@example.org>,
Bharata B Rao <email@example.com>,
Dhaval Giani <firstname.lastname@example.org>,
Balbir Singh <email@example.com>,
Vaidyanathan Srinivasan <firstname.lastname@example.org>,
Srivatsa Vaddagiri <email@example.com>,
Kamalesh Babulal <firstname.lastname@example.org>,
Ingo Molnar <email@example.com>, Pavel Emelyanov <firstname.lastname@example.org>|
|| ||Article, Thread
[ Apologies if you're receiving this twice, the previous mailing did not seem
to make it to the list for some reason ].
Please find attached the latest iteration of bandwidth control (v6).
Where the previous release cleaned up many of the semantics surrounding the
update_curr() path and throttling, this release is focused on cleaning up the
patchset itself. Elements such as the notion of expiring bandwidth from
previous quota periods as well as some of the core accounting changes have
been pushed up (and re-written for clarity) within the patchset reducing the
patch-to-patch churn significantly.
While this restructuring was fairly extensive in terms of the code touched,
there are no major behavioral changes beyond bug fixes.
Thanks to Hidetoshi Seto for identifying the throttle list corruption.
- Runtime is now actively expired taking advantage of the bounds placed on
- distribute_cfs_runtime() no longer races with throttles around the period
- Major code cleanup
- several interactions with active load-balance have been corrected. This was
manifesting previously in throttle_list corruption and crashes.
Three new cgroupfs files are exported by the cpu subsystem:
cpu.cfs_period_us : period over which bandwidth is to be regulated
cpu.cfs_quota_us : bandwidth available for consumption per period
cpu.stat : statistics (such as number of throttled periods and
total throttled time)
One important interface change that this introduces (versus the rate limits
proposal) is that the defined bandwidth becomes an absolute quantifier.
http://lkml.org/lkml/2010/1/5/44 ["CFS Hard limits v5"]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/