© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
It took 14 steps, but finally here is the possible culprit:
19809c2da28aee5
commit 19809c2da28aee5
Author: Michal Hocko <email address hidden>
Date: Mon May 8 15:57:44 2017 -0700
mm, vmalloc: use __GFP_HIGHMEM implicitly
__vmalloc* allows users to provide gfp flags for the underlying
allocation. This API is quite popular
$ git grep "=[[:space:
77
The only problem is that many people are not aware that they really want
to give __GFP_HIGHMEM along with other flags because there is really no
reason to consume precious lowmemory on CONFIG_HIGHMEM systems for pages
which are mapped to the kernel vmalloc space. About half of users don't
use this flag, though. This signals that we make the API unnecessarily
too complex.
This patch simply uses __GFP_HIGHMEM implicitly when allocating pages to
be mapped to the vmalloc space. Current users which add __GFP_HIGHMEM
are simplified and drop the flag.
Link: http://<email address hidden>
Signed-off-by: Michal Hocko <email address hidden>
Reviewed-by: Matthew Wilcox <email address hidden>
Cc: Al Viro <email address hidden>
Cc: Vlastimil Babka <email address hidden>
Cc: David Rientjes <email address hidden>
Cc: Cristopher Lameter <email address hidden>
Signed-off-by: Andrew Morton <email address hidden>
Signed-off-by: Linus Torvalds <email address hidden>
:040000 040000 5cdc1c298cd62f7
:040000 040000 045c832d50bf525
:040000 040000 11f420f52bd9613
:040000 040000 035a87f5c946730
:040000 040000 46bcc13bebdc7f7
:040000 040000 e11579b380817b2
:040000 040000 8357adc979b4be7