>If it's true, then there could be 2 solutions, one is to skip the WARN_ONCE as >it has no practical value, as the real >check is the following code, the other >is to rectify the percpu counter when the policy is changing to >>OVERCOMMIT_NEVER. I think it's better to fix it up when the policy changes. That's the right place. The WARN_ON might be useful to catch other bugs. -Andi
- Re: [PATCH 0/3] make vm_committed_as_batch aware of vm overco... Qian Cai
- Re: [PATCH 0/3] make vm_committed_as_batch aware of vm o... Feng Tang
- RE: [PATCH 0/3] make vm_committed_as_batch aware of ... Kleen, Andi
- Re: [PATCH 0/3] make vm_committed_as_batch aware of ... Michal Hocko