On 12/03/2012 10:55 AM, Michal Privoznik wrote:
> On 30.11.2012 21:55, Laine Stump wrote:
>> On 11/19/2012 11:51 AM, Michal Privoznik wrote:
>>> With current implementation, class ID is just incremented. This can
>>> lead to its exhaustion as tc accepts only 16 bits long identifiers.
>>> Hence, it'
On 30.11.2012 21:55, Laine Stump wrote:
> On 11/19/2012 11:51 AM, Michal Privoznik wrote:
>> With current implementation, class ID is just incremented. This can
>> lead to its exhaustion as tc accepts only 16 bits long identifiers.
>> Hence, it's better if we allow class ID to be reused. To keep tr
On 11/19/2012 11:51 AM, Michal Privoznik wrote:
> With current implementation, class ID is just incremented. This can
> lead to its exhaustion as tc accepts only 16 bits long identifiers.
> Hence, it's better if we allow class ID to be reused. To keep track
> which IDs are free and which are taken
With current implementation, class ID is just incremented. This can
lead to its exhaustion as tc accepts only 16 bits long identifiers.
Hence, it's better if we allow class ID to be reused. To keep track
which IDs are free and which are taken virBitmap is used. This requires
network status file to