Lines Matching refs:to

6 There are two reasons to be requesting non __GFP_WAIT allocations:
8 to incur cost overheads of page stealing and possible swap io for
11 __GFP_IO allocation requests are made to prevent file system deadlocks.
14 to be doing balancing. Page reclamation can be kicked off lazily, that
18 That being said, the kernel should try to fulfill requests for direct
20 the dma pool, so as to keep the dma pool filled for dma requests (atomic
21 or not). A similar argument applies to highmem and direct mapped pages.
22 OTOH, if there is a lot of free dma pages, it is preferable to satisfy
30 been running production machines of varying memory sizes, and seems to be
31 doing fine even with the presence of this problem. In 2.3, due to
37 zone. The good part is, while balancing, we do not need to look at sizes
39 due to ignoring possibly lower usage in the lower class zones. Also,
40 with a slight change in the allocation routine, it is possible to reduce
41 the memclass() macro to be a simple equality.
46 balancing problem, and stays as close to 2.2 behavior as possible. Also,
48 which have different numbers and types of zones. If we wanted to get
49 fancy, we could assign different weights to free pages in different
52 Note that if the size of the regular zone is huge compared to dma zone,
53 it becomes less significant to consider the free dma pages while
54 deciding whether to balance the regular zone. The first solution
60 so as to give a fighting chance for replace_with_highmem() to get a
61 HIGHMEM page, as well as to ensure that HIGHMEM allocations do not
66 kswapd also needs to know about the zones it should balance. kswapd is
70 need to balance the highmem zone, since intr context does not request
72 structure to decide whether a zone needs balancing.
79 are per-zone fields, used to determine when a zone needs to be balanced. When
83 try to free some pages in the zone (providing GFP_WAIT is set in the request).
84 Orthogonal to this, is the decision to poke kswapd to free some zone pages.
92 2. Implement a replace_with_highmem()-like replace_with_regular() to preserve