On Thu, 9 Apr 2015 12:46:09 -0700 (PDT)
David Rientjes wrote:
> It's been merged into that tree, but I would still appreciate your
> ack!
Easy enough.
Acked-by: Jonathan Corbet
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 9 Apr 2015 12:46:09 -0700 (PDT)
David Rientjes rient...@google.com wrote:
It's been merged into that tree, but I would still appreciate your
ack!
Easy enough.
Acked-by: Jonathan Corbet cor...@lwn.net
jon
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Sat, 4 Apr 2015, Jonathan Corbet wrote:
> On Thu, 2 Apr 2015 15:50:15 -0700 (PDT)
> David Rientjes wrote:
>
> > Don't only specify munmap(2) behavior with respect the hugetlb memory, all
> > other syscalls get naturally aligned to the native page size of the
> > processor. Rather, pick
On Sat, 4 Apr 2015, Jonathan Corbet wrote:
On Thu, 2 Apr 2015 15:50:15 -0700 (PDT)
David Rientjes rient...@google.com wrote:
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor.
On Thu, 2 Apr 2015 15:50:15 -0700 (PDT)
David Rientjes wrote:
> Don't only specify munmap(2) behavior with respect the hugetlb memory, all
> other syscalls get naturally aligned to the native page size of the
> processor. Rather, pick out munmap(2) as a specific example.
So I was going to
On Thu, 2 Apr 2015 15:50:15 -0700 (PDT)
David Rientjes rient...@google.com wrote:
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor. Rather, pick out munmap(2) as a specific example.
So I
>
> Don't only specify munmap(2) behavior with respect the hugetlb memory, all
> other syscalls get naturally aligned to the native page size of the
> processor. Rather, pick out munmap(2) as a specific example.
>
> Signed-off-by: David Rientjes
> ---
Acked-by: Hillf Danton
>
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor. Rather, pick out munmap(2) as a specific example.
Signed-off-by: David Rientjes rient...@google.com
---
Acked-by: Hillf Danton
On Thu, 2 Apr 2015, David Rientjes wrote:
> Don't only specify munmap(2) behavior with respect the hugetlb memory, all
> other syscalls get naturally aligned to the native page size of the
> processor. Rather, pick out munmap(2) as a specific example.
>
> Signed-off-by: David Rientjes
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor. Rather, pick out munmap(2) as a specific example.
Signed-off-by: David Rientjes
---
Documentation/vm/hugetlbpage.txt | 7 +--
1 file
On Thu, 2 Apr 2015, David Rientjes wrote:
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor. Rather, pick out munmap(2) as a specific example.
Signed-off-by: David Rientjes
Don't only specify munmap(2) behavior with respect the hugetlb memory, all
other syscalls get naturally aligned to the native page size of the
processor. Rather, pick out munmap(2) as a specific example.
Signed-off-by: David Rientjes rient...@google.com
---
Documentation/vm/hugetlbpage.txt |
12 matches
Mail list logo
