Frank Filz wrote on Fri, Dec 08, 2017 at 07:07:08AM -0800: > > Now that we know every single thread local storage access involves a hidden > > lock/unlock sequence in glibc "magically" invoked by the linker, it would be > > better to remove as many TLS references as possible! > > > > After all, too many lock/unlock are a real performance issue. > > > > Perhaps we should pass op_ctx as the parameter instead. > > I thought the lock was only to create the TLS variable, and not on every > reference.
Yeah, I think the issue is that the first print ever of that thread was at some point that lock was unavailable, but if there had been a previous print it should™ have worked. Not that I understand why the lock wasn't available either... :) -- Dominique ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
