On Thu, Aug 27, 2020 at 10:52 AM Roman Gushchin wrote:
>
> If a memcg to charge can be determined (using remote charging API),
> there are no reasons to exclude allocations made from an interrupt
> context from the accounting.
>
> Such allocations will pass even if the resulting memcg size will
>
If a memcg to charge can be determined (using remote charging API),
there are no reasons to exclude allocations made from an interrupt
context from the accounting.
Such allocations will pass even if the resulting memcg size will
exceed the hard limit, but it will affect the application of the
memo
2 matches
Mail list logo
