hw: explain misleading "Quota exceeded"
Upgrading the quota of a PD session on HW always triggers a "Quota exceeded" warning. To prevent unecessary debugging effort in the future, we explain in an in-code comment that the warning is normal. Ref #1805
This commit is contained in:
parent
6410bd7261
commit
02ef3d13a3
|
@ -114,6 +114,12 @@ void Capability_space::upgrade_slab(Allocator &alloc)
|
||||||
{
|
{
|
||||||
for (;;) {
|
for (;;) {
|
||||||
Slab_block * block;
|
Slab_block * block;
|
||||||
|
|
||||||
|
/*
|
||||||
|
* On every upgrade we try allocating as many blocks as possible.
|
||||||
|
* If the underlying allocator complains that its quota is exceeded
|
||||||
|
* this is normal as we use it as indication when to exit the loop.
|
||||||
|
*/
|
||||||
if (!alloc.alloc(SLAB_SIZE, &block)) return;
|
if (!alloc.alloc(SLAB_SIZE, &block)) return;
|
||||||
block = construct_at<Slab_block>(block, &_slab);
|
block = construct_at<Slab_block>(block, &_slab);
|
||||||
_slab.insert_sb(block);
|
_slab.insert_sb(block);
|
||||||
|
|
Loading…
Reference in New Issue