> This series was extensively reviewed over the past month, and after
> all major comments were merged, I feel it is ready for inclusion when
> the next merge window opens. Minor fixes will be provided if they
> prove to be necessary.
I'm not applying this.
You're turning inline increments and decrements of the existing memory
limits into indirect function calls.
That imposes a new non-trivial cost, in fast paths, even when people
do not use your feature.
Make this evaluate into exactly the same exact code stream we have
now when the memory cgroup feature is not in use, which will be the
majority of users.
OpenVZ Forum
Members
Search
Help
Register
Login
Home
