PLPA Users' Mailing List Archives

Subject: [PLPA users] [PATCH] use max_core_id[socket] as tighter bound for valid core id
From: Bert Wesarg (bert.wesarg_at_[hidden])
Date: 2008-03-21 14:52:59

• Next message: Jeff Squyres: "Re: [PLPA users] plpa in included mode"
• Previous message: Bert Wesarg: "[PLPA users] [PATCH] flatten map_tuple_to_processor_id"
• Next in thread: Jeff Squyres: "Re: [PLPA users] [PATCH] use max_core_id[socket] as tighter bound for valid core id"
• Reply: Jeff Squyres: "Re: [PLPA users] [PATCH] use max_core_id[socket] as tighter bound for valid core id"

In the loop for counting the number of cores in a socket, we don't
need to check all PLPA_BITMASK_CPU_MAX processor ids, only up to
max_core_id[socket] processor ids.

While checking for invalid arguments for map_to_processor_id, the core
argument is checked against '> max_core_id_overall', but we can check
for '> max_core_id[socket]'.

Bert

• text/x-diff attachment: tighter-bounds.patch

• Next message: Jeff Squyres: "Re: [PLPA users] plpa in included mode"
• Previous message: Bert Wesarg: "[PLPA users] [PATCH] flatten map_tuple_to_processor_id"
• Next in thread: Jeff Squyres: "Re: [PLPA users] [PATCH] use max_core_id[socket] as tighter bound for valid core id"
• Reply: Jeff Squyres: "Re: [PLPA users] [PATCH] use max_core_id[socket] as tighter bound for valid core id"