All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Mark Lord <mlord@pobox.com>
Cc: Paul Zimmerman <paulz@synopsys.com>,
	David Laight <David.Laight@ACULAB.COM>,
	"renevant@internode.on.net" <renevant@internode.on.net>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Help testing for USB ethernet/xHCI regression
Date: Fri, 31 Jan 2014 10:37:47 -0800	[thread overview]
Message-ID: <20140131183747.GA18262@xanatos> (raw)
In-Reply-To: <52EB0B51.4020407@pobox.com>

On Thu, Jan 30, 2014 at 09:32:49PM -0500, Mark Lord wrote:
> On 14-01-30 06:26 PM, Sarah Sharp wrote:
> > On Thu, Jan 30, 2014 at 05:20:40PM -0500, Mark Lord wrote:
> >> On 14-01-30 04:41 PM, Sarah Sharp wrote:
> >>>
> >>> Mark and David, can you pull the 3.13-td-changes-reverted branch again,
> >>> and see if the latest patch fixes your issue?  It disables scatter
> >>> gather for the ax88179_178a device, but only when it's operating at USB
> >>> 3.0 speeds.
> >>
> >> As expected, this works just fine.
> > 
> > Did it work when plugged into a USB 2.0 hub?
> 
> Curiosity, NO.  Dies almost immediately when run at USB 2.0 Hi-Speed.
> With a USB 2.0 hub, with a USB 2.0 port on a USB 3.0 hub,
> and with a USB 2.0 extension cable in place of a hub.
> 
> Near instant hangs.
> 
> Plugged directly to the USB 3.0 port, it works fine.

Ok, that makes sense.  The patch I wrote only limited scatter-gather at
USB 3.0 speeds, to see if scatter-gather could work at USB 2.0 speeds.
Reverting commit 3804fad45411b48233b48003e33a78f290d227c8 "USBNET:
ax88179_178a: enable tso if usb host supports sg dma" is the right way
to go instead.

Sarah Sharp

  reply	other threads:[~2014-01-31 18:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <22081260.RNay0J72dY@athas>
2014-01-29 21:54 ` Help testing for USB ethernet/xHCI regression Sarah Sharp
2014-01-30  9:44   ` David Laight
2014-01-30 10:46     ` renevant
2014-01-30 12:46       ` renevant
     [not found]     ` <063D6719AE5E284EB5DD2968C1650D6D0F6ACF20-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-01-30 18:44       ` Sarah Sharp
2014-01-30 19:45         ` Mark Lord
2014-01-30 19:54         ` Paul Zimmerman
     [not found]           ` <A2CA0424C0A6F04399FB9E1CD98E03046D147453-Yu2iAY70zvrYN67daEjeMPufCSb+aD3WLzEdoUbNIic@public.gmane.org>
2014-01-30 20:00             ` Mark Lord
2014-01-30 21:41               ` Sarah Sharp
2014-01-30 22:20                 ` Mark Lord
     [not found]                   ` <52EAD038.5020409-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2014-01-30 23:26                     ` Sarah Sharp
2014-01-31  2:32                       ` Mark Lord
2014-01-31 18:37                         ` Sarah Sharp [this message]
2014-01-28 20:30 Sarah Sharp
2014-01-29  4:30 ` Mark Lord
2014-01-29  4:54   ` Mark Lord
2014-01-29 21:18   ` Sarah Sharp
2014-01-30 10:03     ` David Laight
2014-01-30 21:45     ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140131183747.GA18262@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulz@synopsys.com \
    --cc=renevant@internode.on.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.