On Thu, Jun 27, 2002, Soewono Effendi <[EMAIL PROTECTED]> wrote: > after looking around in source codes and searching in mailing list and G*gle, > I still couldn't find any hints why there exists only one "khubd" in USB Stack. > Isn't it "better (performance?)" to have one "khubd" for each HC? (thinking of multi >processor platform) > What was the design/implementation decision?
Simplicity. If we have multiple khubd threads, then we can process insertions and removals for multiple devices at the same time. That would require extra complexity in driver probe routines. Also, there just didn't seem to be the need for processing multiple device insertions at the same time. It doesn't happen often. The only time that really happens is at boot time. That being said, it's not a complicated process to use multiple khubd threads as well as clean up the drivers, but unless there's a reason for it, I'd rather not make things more complicated for the sake of making it more complicated. > Is there any informations about "URB lifetime" ? who allocates and deallocates it, > when one should/shouldn't remove it, etc. The driver allocates and deallocates the URB in all cases. It may unlink (I'm guessing what you mean by "remove") at anytime after it has been submitted. JE ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
