Thread (9 messages) 9 messages, 2 authors, 2018-09-13

Re: [PATCH v3 3/3] docs: core-api: add memory allocation guide

From: Jonathan Corbet <corbet@lwn.net>
Date: 2018-09-13 22:41:32
Also in: linux-mm, lkml

On Wed, 12 Sep 2018 13:33:06 +0300
Mike Rapoport [off-list ref] wrote:
How about:

    ``GFP_HIGHUSER_MOVABLE`` does not require that allocated memory
    will be directly accessible by the kernel and implies that the
    data is movable.

    ``GFP_HIGHUSER`` means that the allocated memory is not movable,
    but it is not required to be directly accessible by the kernel. An
    example may be a hardware allocation that maps data directly into
    userspace but has no addressing limitations.

    ``GFP_USER`` means that the allocated memory is not movable and it
    must be directly accessible by the kernel
Sounds good to me.

Thanks,

jon
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help