Messages in this thread | | | Date | Tue, 15 Jun 2004 07:40:04 +1000 | From | Anton Blanchard <> | Subject | Re: NUMA API observations |
| |
> interleave should always fall back to other nodes. Very weird. > Needs to be investigated. What were the actual arguments passed > to the syscalls?
This one looks like a bug in my code. I wasnt setting numnodes high enough, so the node fallback lists werent being initialised for some nodes.
> > My kernel is compiled with NR_CPUS=128, the setaffinity syscall must be > > called with a bitmap at least as big as the kernels cpumask_t. I will > > submit a patch for this shortly. > > Umm, what a misfeature. We size the buffer up to the biggest > running CPU. That should be enough. > > IMHO that's just a kernel bug. How should a user space > application sanely discover the cpumask_t size needed by the kernel? > Whoever designed that was on crack.
glibc now uses a select style interface. Unfortunately the interface has changed about three times by now.
> I will probably make it loop and double the buffer until EINVAL ends or it > passes a page and add a nasty comment.
Perhaps we could use the new glibc interface and fall back to the loop on older glibcs.
Anton - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |