On Thu, Oct 25, 2012 at 9:40 AM, Minchan Kim minchan@kernel.org wrote:
Your description doesn't include why we need new vmevent_fd(2). Of course, it's very flexible and potential to add new VM knob easily but the thing we is about to use now is only VMEVENT_ATTR_PRESSURE. Is there any other use cases for swap or free? or potential user? Adding vmevent_fd without them is rather overkill.
What ABI would you use instead?
On Thu, Oct 25, 2012 at 9:40 AM, Minchan Kim minchan@kernel.org wrote:
I don't object but we need rationale for adding new system call which should be maintained forever once we add it.
Agreed.