On Thu, Jan 31, 2019 at 1:18 AM Martynas Pumputis <m...@lambda.lt> wrote: > > Previously, bpf_num_possible_cpus() had a bug when calculating a > number of possible CPUs in the case of sparse CPU allocations, as > it was considering only the first range or element of > /sys/devices/system/cpu/possible. > > E.g. in the case of "0,2-3" (CPU 1 is not available), the function > returned 1 instead of 3. > > This patch fixes the function by making it parse all CPU ranges and > elements. > > Signed-off-by: Martynas Pumputis <m...@lambda.lt>
Acked-by: Yonghong Song <y...@fb.com>
