Em Mon, Mar 30, 2015 at 11:58:05AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Mon, Mar 30, 2015 at 09:48:52PM +0900, Namhyung Kim escreveu: > > But this makes every sample processing grabs and releases the lock so > > might cause high overhead. It can be a problem if such processing is > > done parallelly like my multi-thread work. :-/ > > Still untested, using rw lock, next step is auditing the > machine__findnew_thread users that really should be using > machine__find_thread, i.e. grabbing just the reader lock, and measuring > the overhead of using a pthread rw lock instead of pthread_mutex_t as > Jiri is doing.
Don't bother trying it, doesn't even compile ;-\ As I said, untested, more as a heads up, will fix it up properly and test after lunch. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
