Re: device struct bloat
Peter Zijlstra <[email protected]>
| Newsgroups | gmane.linux.usb.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <1194342534.6544.25.camel@twins> |
On Mon, 2007-11-05 at 14:49 -0800, Greg KH wrote: > On Mon, Nov 05, 2007 at 11:57:14AM +0100, Peter Zijlstra wrote: > > Hmm, the problem seems to be stuff like: > > > > add usb driver to pci > > scan pci devices > > add usb host controller device > > scan usb devices > > add usb hub device > > scan usb devices > > add usb ..... > > > > This seems to be able to go on forever, as long as one can cascade usb > > hubs. > > USB hubs only work 7 deep, so there is a limit. Ah, missed that bit of knowledge :-) > > Doesn't seem like an ideal thing to do from a stack space POV either. > > > > Would it be possible to break at the second scan, that is the device > > probe and stick that into a workqueue or something. Then we'd only ever > > have driver->device nesting. > > Alan and Oliver have done some work in this area I think, combined with > the suspend/bind/unbind issues. I'll let them comment on your patch :) Great, so the thing I need to make this work nicely is a limited device->mutex nesting, if these changes result in that we can work together to finish this conversion. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel