From: David Laight <David.Laight@xxxxxxxxxx> Date: Fri, 23 May 2014 08:52:13 +0000 > The hardware will put multiple ethernet frames into a single USB bulk data > message. To handle this the driver generates a URB that is (hopefully) long > enough for the longest USB message (typically 32k is assumed to be enough). > The URB that usb_net generated have the data in a linear skb - which then > has a large 'truesize'. > > Since USB bulk data are terminated by a short fragment there is actually > no need for the URB be long enough for the full message. Provided the > URB are multiples of the USB message size (1k for USB 3) the message > can be received into multiple URB - the driver just has to be willing > to merge URB buffers (as well as split them) when generating the ethernet > frames. I think we could take a less invasive approach. Use whatever order page is needed for that 32K chunk for the URB, but split up the compound page so that the individual pages can be accounted for separately. Hook up the pages into the SKB frag array, and only account PAGE_SIZE into the SKB truesize for the individual pages actually used from the superpage. This will largely retain the URB allocation and processing scheme, yet at the same time dramatically decrease the truesize overrage factor. > What the driver needs to do us allocate URB with 2k (or 4k) buffers and > only allocate the skb when processing the receive data. > Unfortunately this is a major rework of usb_net.c > Note that some of the usb ethernet drivers allocate large skb then > lie about the truesize. Which has to be fixed, as Eric explained. -- 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
