include/linux/nodemask.h: Use nr_node_ids instead of MAX_NUMNODES in nodemask_pr_args
PATCH 1/1 include/linux/nodemask.h: Use nr_node_ids instead of MAX_NUMNODES in nodemask_pr_args
When viewing the /proc/<pid>/status file, one can see output lines like
Cpus_allowed: ffffffff,ffffffff,ffffffff
Cpus_allowed_list: 0-95
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f
Mems_allowed_list: 0-3
It looks really strange that so many bits are displayed in the "Mems_allowed:" line. Whereas the "Cpus_allowed:" line is perfectly fine.
It is because the nodemask_pr_args() macro uses MAX_NUMNODES as the number of nodes to iterate. The cpumask_pr_args() macro uses nr_cpu_ids instead of MAX_CPUS. For nodes, there is a corresponding nr_node_ids. So it makes sense to use nr_node_ids instead to be consistent with "Cpus_allowed:".
With that change, the "Mems_allowed:" line becomes
Mems_allowed: f
--- include/linux/nodemask.h | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
include/linux/nodemask.h +3 -4
@@ -97,6 +97,8 @@ typedef struct { DECLARE_BITMAP(bits, MAX_NUMNODES); } nodemask_t;extern nodemask_t _unused_nodemask_arg_; +extern int nr_node_ids; +extern int nr_online_nodes;/** * nodemask_pr_args - printf args to output a nodemask
@@ -108,7 +110,7 @@__nodemask_pr_bits (maskp) static inline unsigned int __nodemask_pr_numnodes(const nodemask_t *m) { -return m ?MAX_NUMNODES :0 ; +return m ? nr_node_ids :0 ; }static inline const unsigned long *__nodemask_pr_bits (const nodemask_t *m) {
@@ -444,9 +446,6 @@ static inline int next_memory_node(int nid)return next_node (nid, node_states[N_MEMORY ]); } -extern int nr_node_ids; -extern int nr_online_nodes; -static inline void node_set_online (int nid) {node_set_state (nid,N_ONLINE );
Signature · 1 line
1.8.3.1
Quoted 6 lines · On Tue, 18 Dec 2018 12:30:31 -0500 Waiman Long <[email protected]> wrote:
When viewing the /proc/<pid>/status file, one can see output lines like
Cpus_allowed: ffffffff,ffffffff,ffffffff
Cpus_allowed_list: 0-95
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f
Mems_allowed_list: 0-3
Oh dear.
Quoted 10 lines
It looks really strange that so many bits are displayed in the "
Mems_allowed:" line. Whereas the "Cpus_allowed:" line is perfectly fine.It is because the
nodemask_pr_args()macro usesMAX_NUMNODESas the number of nodes to iterate. Thecpumask_pr_args()macro usesnr_cpu_idsinstead ofMAX_CPUS. For nodes, there is a correspondingnr_node_ids. So it makes sense to usenr_node_idsinstead to be consistent with "Cpus_allowed:".
Quoted 3 lines
With that change, the "
Mems_allowed:" line becomes
Mems_allowed: f
OK, I guess. There is a risk of breaking existing userspace, but any half-decent parser should treat the above as equivalent.
However there are quite a lot of nodemask_pr_args() callers in the tree and this patch potentially changes behaviour at all those sites. Please work through all those callers and show how the output is altered so we can consider the patch's complete effect.
Quoted 22 lines · Andrew Morton
Quoted 6 lines · On Tue, 18 Dec 2018 12:30:31 -0500 Waiman Long <[email protected]> wrote:
When viewing the /proc/<pid>/status file, one can see output lines like
Cpus_allowed: ffffffff,ffffffff,ffffffff
Cpus_allowed_list: 0-95
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f
Mems_allowed_list: 0-3Oh dear.
Quoted 12 lines
It looks really strange that so many bits are displayed in the "
Mems_allowed:" line. Whereas the "Cpus_allowed:" line is perfectly fine.It is because the
nodemask_pr_args()macro usesMAX_NUMNODESas the number of nodes to iterate. Thecpumask_pr_args()macro usesnr_cpu_idsinstead ofMAX_CPUS. For nodes, there is a correspondingnr_node_ids. So it makes sense to usenr_node_idsinstead to be consistent with "Cpus_allowed:".With that change, the "
Mems_allowed:" line becomes
Quoted 10 lines
Quoted 1 line
Mems_allowed: fOK, I guess. There is a risk of breaking existing userspace, but any half-decent parser should treat the above as equivalent.
However there are quite a lot of
nodemask_pr_args()callers in the tree and this patch potentially changes behaviour at all those sites. Please work through all those callers and show how the output is altered so we can consider the patch's complete effect.
The /proc/<pid>/status file is the only one that will be affected by this patch. I believe the "Mems_allowed_list" is what most users are using, not the "Mems_allowed".
Cheers,
Longman