On Friday 31 July 2009 18:34:26 Attilio Rao wrote: > 2009/7/31 Hans Petter Selasky <hselasky_at_c2i.net>: > > Hi, > > > > Speaking about the USB subsystem and newbus: > > Hans, > I wanted to maintain this private to us but you clearly don't > understand what races live in newbus, what requirements in locking we > need to protect that and also how a sane locking scheme should be > built. > Please drop this conversation. Hi, I'm not saying that your approach will not work or that it is wrong. I'm saying that it is not fast enough. Your patch affects the boottime, in a negative way. Sure I can help you eliminate blocking the whole USB explore thread from newbus_lock(), but there are sometimes also synchronous delay inside device probe functions, and I think for those cases it would be better if we kept using Giant, because then all sleep calls have drop- and pickup- Giant code, but there is no automatic drop and pickup for the newbus_lock()! How can we multi-thread the boot-sequence given your newbus_lock() requirement ? --HPSReceived on Fri Jul 31 2009 - 15:19:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:53 UTC