Thread (6 messages) 6 messages, 3 authors, 2012-10-29

Re: [V5 PATCH 08/26] memcontrol: use N_MEMORY instead N_HIGH_MEMORY

From: David Rientjes <hidden>
Date: 2012-10-29 21:08:10
Also in: linux-mm, lkml

Possibly related (same subject, not in this thread)

On Mon, 29 Oct 2012, Michal Hocko wrote:
quoted
quoted
quoted
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
What is the difference of those two?
Patch 5 in the series 
Strange, I do not see that one at the mailing list.
http://marc.info/?l=linux-kernel&m=135152595827692
quoted
introduces it to be equal to N_HIGH_MEMORY, so 
So this is just a rename? If yes it would be much esier if it was
mentioned in the patch description.
It's not even a rename even though it should be, it's adding yet another 
node_states that is equal to N_HIGH_MEMORY since that state already 
includes all memory.  It's just a matter of taste but I think we should be 
renaming it instead of aliasing it (unless you actually want to make 
N_HIGH_MEMORY only include nodes with highmem, but nothing depends on 
that).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help