This patchset contains patches for PID allocation. Individual patches in the series break the kernel. But once, the patchset is applied, the kernel compiles. We have to figure out whether to send this as one whole patch or if to send in a series, how to break the patches so that it does not break the kernel. Rik proposed to ways to test the changes made: - Create a fork, if the child's pid is greater than the parent's pid, we can see that the allocation is done correctly. - Create several containers inside a Docker and see how PID allocation is being done since every container should have a separate PID namespace. I'm yet to figure out how to go about doing these tests. I also wanted to know if there would be a way to figure out if PID operations are now actually faster or not. ANy recommendations on how to go about doing this? Gargi Sharma (8): pid_namespace: destroy_pid_namespace: Add IDR implementation pid_namespace: zap_pid_ns_processes: Add IDR implementation pid.c: Add IDR implementation for alloc_pid and free_pid pid.c: Add implementation for find_ge_pid pid.c: Delete free_pidmap(), alloc_pidmap(), next_pidmap() pid.c: Delete mk_pid(), pid_before(), set_last_pid() pid.c: IDR implementation for pidmap_init() pid_namespace: IDR implementation for create_pid_namespace include/linux/pid_namespace.h | 5 +- init/main.c | 2 +- kernel/pid.c | 184 ++++++------------------------------------ kernel/pid_namespace.c | 36 +++------ 4 files changed, 43 insertions(+), 184 deletions(-) -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
