Skip to content

__GFP_REPEAT cleanup

[email protected] linux-arch linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3tree wide: get rid of __GFP_REPEAT for order-0 allocations part Iarch/alpha/include/asm/pgalloc.h arch/arm/include/asm/pgalloc.h arch/avr32/include/asm/pgalloc.h +24 more+47 -528 replies
2/3tree wide: get rid of __GFP_REPEAT for small order requestsarch/arc/include/asm/pgalloc.h arch/arm/include/asm/pgalloc.h arch/arm/mm/pgd.c +8 more+16 -190 replies
3/3jbd2: get rid of superfluous __GFP_REPEATfs/jbd2/journal.c+6 -97 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] __GFP_REPEAT cleanup

Hi,
while working on something unrelated I've checked the current usage of __GFP_REPEAT in the tree. It seems that a good half of it is and always has been bogus because __GFP_REPEAT has always been about high order allocations while we are using it for order-0 or very small orders very often. It seems that a big pile of them is just a copy&paste when a code has been adopted from one arch to another.

I think it makes some sense to get rid of them because they are just making the semantic more unclear.

The series is based on linux-next tree and

$ git grep __GFP_REPEAT next/master | wc -l
106

and with the patch

$ git grep __GFP_REPEAT  | wc -l
44

There are probably more users which do not need the flag but I have focused on the trivially superfluous ones here.

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