Messages in this thread Patch in this message | | | From | Mel Gorman <> | Subject | [PATCH 12/25] Remove a branch by assuming __GFP_HIGH == ALLOC_HIGH | Date | Fri, 20 Mar 2009 10:02:59 +0000 |
| |
Allocations that specify __GFP_HIGH get the ALLOC_HIGH flag. If these flags are equal to each other, we can eliminate a branch.
[akpm@linux-foundation.org: Suggested the hack] Signed-off-by: Mel Gorman <mel@csn.ul.ie> --- mm/page_alloc.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c index ad26052..1e8b4b6 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -1640,8 +1640,8 @@ gfp_to_alloc_flags(gfp_t gfp_mask) * policy or is asking for __GFP_HIGH memory. GFP_ATOMIC requests will * set both ALLOC_HARDER (!wait) and ALLOC_HIGH (__GFP_HIGH). */ - if (gfp_mask & __GFP_HIGH) - alloc_flags |= ALLOC_HIGH; + VM_BUG_ON(__GFP_HIGH != ALLOC_HIGH); + alloc_flags |= (gfp_mask & __GFP_HIGH); if (!wait) { alloc_flags |= ALLOC_HARDER; -- 1.5.6.5
| |