After (weighted) slot quotas are assigned to all the group entries, surplus sharing is computed for all groups in the hierarchy configured to accept surplus. Following surplus sharing, when slot weighting is not enabled, any fractional quota allocations are consolidated and distributed in a round robin fashion.
{subsubsection: Surplus Sharing}
+The primary purpose of surplus sharing is to allow group quotas to "float" locally based on demand. For example, if one configures group A, A.B, and A.C, where gropup A does not share surplus, but A.B and A.C do share surplus, then A.B and A.C can float against each other, while maintaining the constraint that quota(A.B) + quota(A.C) <= quota(A). Surplus quota is always shared at the lowest possible level before being passed upwards.
+
The basic principle for surplus sharing is: surplus quota is distributed among sibling groups in proportion to assigned quota. For example, if group A has twice the quota of group B, group A will be awarded twice the surplus. Some additional points:
*: available surplus consists of any surplus shared from the level above in the hierarchy, plus any surplus coming up from sibling sub-trees
*: any groups with surplus sharing not enabled do not participate in surplus distribution
