From: Cliff Wickman <cpw@xxxxxxx> Maintain compatibility for codes using version 2.0.3 numa_num_thread_nodes() and numa_num_thread_cpus(). The man page will only document the new names. The qthreads package, for example, still calls the "thread" names. Signed-off-by: Cliff Wickman <cpw@xxxxxxx> --- libnuma.c | 18 ++++++++++++++++++ numa.h | 2 ++ versions.ldscript | 2 ++ 3 files changed, 22 insertions(+) Index: numactl-dev/libnuma.c =================================================================== --- numactl-dev.orig/libnuma.c +++ numactl-dev/libnuma.c @@ -635,6 +635,15 @@ numa_num_task_nodes(void) return maxprocnode+1; } +/* + * for backward compatibility + */ +int +numa_num_thread_nodes(void) +{ + return numa_num_task_nodes(); +} + int numa_num_task_cpus(void) { @@ -642,6 +651,15 @@ numa_num_task_cpus(void) } /* + * for backward compatibility + */ +int +numa_num_thread_cpus(void) +{ + return numa_num_task_cpus(); +} + +/* * Return the number of the highest node in this running system, */ int Index: numactl-dev/versions.ldscript =================================================================== --- numactl-dev.orig/versions.ldscript +++ numactl-dev/versions.ldscript @@ -125,6 +125,8 @@ libnuma_1.2 { numa_num_possible_nodes; numa_num_task_cpus; numa_num_task_nodes; + numa_num_thread_cpus; + numa_num_thread_nodes; numa_pagesize; numa_parse_bitmap; numa_parse_cpustring; Index: numactl-dev/numa.h =================================================================== --- numactl-dev.orig/numa.h +++ numactl-dev/numa.h @@ -260,9 +260,11 @@ int numa_num_configured_cpus(); /* maximum cpus allowed to current task */ int numa_num_task_cpus(); +int numa_num_thread_cpus(); /* backward compatibility */ /* maximum nodes allowed to current task */ int numa_num_task_nodes(); +int numa_num_thread_nodes(); /* backward compatibility */ /* allocate a bitmask the size of the kernel cpumask_t */ struct bitmask *numa_allocate_cpumask(); -- To unsubscribe from this list: send the line "unsubscribe linux-numa" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html