On Wed, May 28, 2014 at 21:45:41 -0400, Naoya Horiguchi wrote: > > The user could also mark more than > > one thread in this way - in which case the kernel will pick > > the first one it sees (is that oldest, or newest?) that is marked. > > Not sure if this would ever be useful unless you want to pass > > responsibility around in an application that is dynamically > > creating and removing threads. > > I'm not sure which is better to send signal to first-found marked thread > or to all marked threads. If we have a good reason to do the latter, > I'm ok about it. Any idea? Well, it would be more flexible if the signal were sent to all marked threads, but I don't know if that constitutes a good enough reason to add the extra complexity involved. Sometimes better is the enemy of good, and in this case the patch you proposed should be good enough for any practical case I can think of. Naoya, Tony, thank you for taking the leadership on this issue and seeing it through, and for the courtesy of keeping me in the loop! Kamil -- Kamil Iskra, PhD Argonne National Laboratory, Mathematics and Computer Science Division 9700 South Cass Avenue, Building 240, Argonne, IL 60439, USA phone: +1-630-252-7197 fax: +1-630-252-5986 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>