Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
- From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 14 Sep 2007 10:34:40 -0400 (EDT)
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
- From: Matthew Dharm
- Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
- Prev by Date: Re: Driver core: remove get_bus()
- Next by Date: Re: [NFS] [PATCH 2/7] NFS: if ATTR_KILL_S*ID bits are set, then skip mode change
- Previous by thread: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
- Next by thread: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
- Index(es):