Re: net2280: tracing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

cheers

-- 
balbi

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux