Re: [PATCH 0/3] userfaultfd: non-cooperative: add madvise() event for MADV_REMOVE request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jan 19, 2017 at 10:22:31AM +0200, Mike Rapoport wrote:
> Hi,
> 
> These patches add notification of madvise(MADV_REMOVE) event to
> non-cooperative userfaultfd monitor.
> 
> The first pacth renames EVENT_MADVDONTNEED to EVENT_REMOVE along with
> relevant functions and structures. Using _REMOVE instead of _MADVDONTNEED
> describes the event semantics more clearly and I hope it's not too late for
> such change in the ABI.
> 
> The patches are against current -mm tree.

Reviewed-by: Andrea Arcangeli <aarcange@xxxxxxxxxx>

Not sure if they should be folded inside -mm before they go upstream,
but if they're sent all along it probably doesn't make a difference,
it just adds one more handler.

In theory we could have differentiated MADV_REMOVE and MADV_DONTNEED
in two different events, but I couldn't see any downside in sharing
the same event for both and this looks more compact.

Thanks,
Andrea

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]
  Powered by Linux