On 7/17/24 21:24, Tejun Heo wrote:
On Wed, Jul 17, 2024 at 07:48:40PM -0400, Waiman Long wrote:
...
How about letting .peak shows two numbers? The first one is the peak since
the creation of the cgroup and cannot be reset. The second one is a local
maximum that can be reset to 0. We just to keep track of one more counter
that should be simple enough to implement.
What Johannes suggested seems to hit all the marks - it's efficient and
relatively simple, the overhead is only on the users of the facility, and
flexible in a straightforward manner. I have a hard time buying the argument
that it's more difficult to use - the benefit to cost ratio seems pretty
clear. Given that, I'm not sure why we'd want to add something fishy that
can lead to longterm problems.
On second thought, it is a change in the user interface that may break
existing apps that use the peak file. So it is probably better to go
with Johannes' suggestion.
Thanks,
Longman
