On 12/29/2014 02:58 PM, Felipe Balbi wrote: > Hi, > > On Mon, Dec 29, 2014 at 02:56:25PM -0500, Jorge Ramirez-Ortiz wrote: >> On 12/29/2014 11:37 AM, Felipe Balbi wrote: >>> Hi, >>> >>> On Sun, Dec 28, 2014 at 07:28:33PM -0500, Jorge Ramirez-Ortiz wrote: >>>> On 12/28/2014 11:39 AM, Felipe Balbi wrote: >>>>> On Sat, Dec 27, 2014 at 05:33:36PM -0500, Jorge Ramirez-Ortiz wrote: >>>>>> Hi Ricardo/all >>>>>> >>>>>> I finally got around to capture a trace of a SS bulk transfer using the net2280. >>>>>> The trace is available to anyone interested (70 MB file for the Beaglebone 5000). >>>>> can you publish the trace somewhere we can download ? I use Beagle5000 >>>>> myself and could help revieweing the traces. >>>>> >>>> Thanks Felipe. >>>> I dont have any public ftp server at hand so I just pushed the log to my Xenomai >>>> git tree. >>>> >>>> please grab it from here (no need to clone the tree, just press the download link) >>>> http://git.xenomai.org/xenomai-jro.git/commit/?h=logs >>> One of the reasons could be because you're using the printer gadget :-) >>> Have you tried any of the other gadgets ? In any case, try this little >>> hack: >>> >>> diff --git a/drivers/usb/gadget/legacy/printer.c b/drivers/usb/gadget/legacy/printer.c >>> index 9054598..8a09661 100644 >>> --- a/drivers/usb/gadget/legacy/printer.c >>> +++ b/drivers/usb/gadget/legacy/printer.c >>> @@ -129,7 +129,7 @@ module_param(qlen, uint, S_IRUGO|S_IWUSR); >>> >>> /* holds our biggest descriptor */ >>> #define USB_DESC_BUFSIZE 256 >>> -#define USB_BUFSIZE 8192 >>> +#define USB_BUFSIZE 65536 >>> >>> static struct usb_device_descriptor device_desc = { >>> .bLength = sizeof device_desc, >> yes I thought about that as well: in fact the trace I made available already had >> that modification in place. >> (it also has the queue length increased to 20 - no more changes after those two) > oh, ok. That would mean the IP can't pump more data :-s > >> for simplicity -and to have a common test vehicle- I'll capture a trace using >> the g_mass_storage (last time I run that check the performance numbers were >> exactly the same though). >> To use g_printer I wrote a small application service on the device side (I can >> push it to the same place I put the previous log if you want? let me know) > just out of curiosity, how many PCIe lanes are you using with your PLX > device ? That could be a limitting factor. I am using a GEN2 port: 1x PCIe GEN2: HH/HL x1 mechanical, x1 electrical according to the spec "Each Root Port x1 lane supports up to 5 Gb/s bandwidth in each direction (10 Gb/s concurrent)" So I believe this should be sufficient. here is the spec: http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/8-series-chipset-pch-datasheet.pdf and this is the system that contains the plx device http://shop.lenovo.com/us/en/servers/thinkserver/towers/ts140/#tab-tech_specs from the lshw (plx device is the 338x using the net2280 driver) *-pci:1 description: PCI bridge product: 8 Series/C220 Series Chipset Family PCI Express Root Port #2 vendor: Intel Corporation physical id: 1c.1 bus info: pci@0000:00:1c.1 version: d4 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:25 ioport:2000(size=4096) memory:f7c00000-f7cfffff ioport:df200000(size=2097152) *-usb description: USB controller product: PLX Technology, Inc. vendor: PLX Technology, Inc. physical id: 0 bus info: pci@0000:02:00.0 version: ab width: 32 bits clock: 33MHz capabilities: pm msi pciexpress usb_device bus_master cap_list rom configuration: driver=net2280 latency=0 resources: irq:34 memory:f7c28000-f7c29fff memory:f7c10000-f7c1ffff memory:f7c00000-f7c0ffff memory:f7c20000-f7c27fff > > cheers > -- 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
