On Fri, Jul 14, 2017 at 09:03:08AM +0530, Gargi Sharma wrote: > 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? Why did you send this to linux-usb@vger? How does it relate to the kernel's USB subsystem? thanks, greg k-h -- 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
