lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <806dafc20608041323v5c1fecd6we801df9353a2d87d@mail.gmail.com>
Date:	Fri, 4 Aug 2006 16:23:54 -0400
From:	"Christopher Montgomery" <xiphmont@...il.com>
To:	"David Brownell" <david-b@...bell.net>
Cc:	linux-usb-devel@...ts.sourceforge.net,
	"Matthias Schniedermeyer" <ms@...d.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [linux-usb-devel] Stability-Problem of EHCI with a larger number of USB-Hubs/Devices

On 8/4/06, David Brownell <david-b@...bell.net> wrote:
> Did you try with 2.6.18-rc3?  There's a Kconfig option for an
> improved interrupt scheduler, which might help especially with
> all those low speed devices.

Actually, assuming I'm reading the spec right, I've come to realize
Dan's improved scheduler patch allows illegal QH schedules that the
old scheduler prevented (as the old scheduler would not allow any set
of complete splits to overlap).  Dan's patch allows complete splits to
be serviced in a different order than the original start splits, which
will cause the out of order responses to be dropped on the floor.

QHs splits must be scheduled in the order the QHs appear in a given
frame; if QH B is scheduled after QH A and uses a later microframe for
its SS, but appears in a higher period level of the tree such that it
actually occurs earlier in the frame, QH A may see all of its complete
splits lost; this is subject to uncertainties due to bti stuffing and
bandwidth recovery/error recovery.  It is possible in our current
scheduler with Dan's improvement patch.

Monty
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ