On Tue, Jul 30, 2013 at 11:33:29AM -0700, David Miller wrote: > From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> > Date: Tue, 30 Jul 2013 07:00:59 -0700 > > > This call is so slow, you can afford to make a call to kmalloc for the > > data, as it sure just did for other structures it needed :) > > I told him to implement things this way, to avoid calling kmalloc every > single register access. > > Using kmalloc all the time makes the access fragile, since a badly timed > call during high memory pressure can fail. > > I'd rather the potential failure happen at one time, probe time. I agree, but the call usb_control_message() also does a tiny kmalloc(), and is _very_ slow and if you have high memory pressure, doing USB messages like this is not what you want to do anyway (the host controller does it's own allocations and the like as well.) USB isn't "fast" like most normal networking physical layers :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
