On Fri, 8 Jul 2005, vitko wrote: > > There's no obvious reason for this. Unless you are encountering some sort > > of error during your transfers, causing some of the operations to be > > retried? If there were any errors, they would should up in the log when > > you turn on CONFIG_USB_STORAGE_DEBUG. > > No errors at all when running "normal" kernel. As for CONFIG_USB_DEBUG and > CONFIG_USB_STORAGE_DEBUG enabled kernel, please see dmesg output below.
The striking thing about your log is that all the commands are WRITEs and they are all relatively short. Is the speed for reading better than the speed for writing? Someone had a very similar problem not too long ago (a month or two). It turned out that the slowdown was related not to the kernel but to the distribution, although the exact cause was never determined. Anyway, this looks like you are writing to a filesystem that was mounted with -o sync or something similar. You might find it interesting to try doing the exact same write transfer under both 2.6.11 and 2.6.12, with usb-storage debugging turned on for both systems, and then compare the debugging logs. If the timings are so drastically different then I would expect the sequence of commands to be different as well. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
