linux-kernel - Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6

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: <Pine.LNX.4.44L0.0709141031450.3782-100000@iolanthe.rowland.org>
Date:	Fri, 14 Sep 2007 10:34:40 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Matthew Dharm <mdharm-kernel@...-eyed-alien.net>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...sta.de>, Adrian Bunk <bunk@...nel.org>,
	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	Oliver Neukum <oneukum@...e.de>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6

On Thu, 13 Sep 2007, Matthew Dharm wrote:

> > In fact, setting max_sectors down to 64 is probably overkill -- 120
> > ought to be enough.  But there may have been one or two oddball devices
> > that really did have a 32-KB limit, and better safe than sorry.  At one
> > point an engineer from Genesys said their devices did, although they do
> > seem to work perfectly well with 64-KB transfers (and that's what 
> > Windows gives them).
> 
> It's worth pointing out that performance drops like a stone as this number
> goes down.

Does anybody have good performance figures, using a high-quality
device?  This is the sort of thing where it helps to have some real
numbers.

Alan Stern

-
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/