From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "David Laight" <David.Laight@ACULAB.COM>,
"Mark Lord" <mlord@pobox.com>, netdev <netdev@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Bjørn Mork" <bjorn@mork.no>, "Freddy Xin" <freddy@asix.com.tw>,
"Ming Lei" <ming.lei@canonical.com>
Subject: Re: [RFT 1/2] xhci 1.0: Limit arbitrarily-aligned scatter gather.
Date: Wed, 5 Feb 2014 13:45:07 -0800 [thread overview]
Message-ID: <20140205214507.GF12087@xanatos> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1402051619240.1312-100000@iolanthe.rowland.org>
On Wed, Feb 05, 2014 at 04:23:50PM -0500, Alan Stern wrote:
> On Wed, 5 Feb 2014, Sarah Sharp wrote:
>
> > On Wed, Feb 05, 2014 at 11:58:12AM +0000, David Laight wrote:
>
> > > The problem is that the ax88179_178a driver submits receive URBs that
> > > cross 64k boundaries, and are not aligned (they start at an 0x40 boundary).
> > > Receive USB frames can contain multiple ethernet frames, by default they
> > > are 20kB (and sit in 24kB of memory).
> >
> > Perhaps you should add printks when a TRB is split on 64KB boundaries
> > and see if the device drops packets around that time?
>
> This seems kind of puzzling.
>
> In theory, any URB that's more than 1 byte long can cross a 64-KB
> boundary. I don't understand why this should cause problems for
> xhci-hcd. Sure, the transfer has to be split into multiple TDs where
> the boundary crossing occurs. But why would that be problematic?
If we split a non-scatter gather URB into two TRBs because of the 64-KB
boundary rule, and we have to put a link TRB in between them, that may
violate the TD fragments rule for 1.0 hosts.
So the debugging should really only trigger when there's a link TRB in
between two TRBs on the bulk ring.
Sarah Sharp
next prev parent reply other threads:[~2014-02-05 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1391544195.git.sarah.a.sharp@linux.intel.com>
[not found] ` <baa32650c285a89671030370f638e2203171b3a0.1391544195.git.sarah.a.sharp@linux.intel.com>
2014-02-05 11:58 ` [RFT 1/2] xhci 1.0: Limit arbitrarily-aligned scatter gather David Laight
2014-02-05 21:08 ` Sarah Sharp
2014-02-05 21:23 ` Alan Stern
2014-02-05 21:45 ` Sarah Sharp [this message]
2014-02-05 22:40 ` Peter Stuge
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=20140205214507.GF12087@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=bjorn@mork.no \
--cc=freddy@asix.com.tw \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=mlord@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).