From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Greg KH <gregkh@suse.de>, Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Increase USBFS Bulk Transfer size
Date: Wed, 12 Oct 2011 17:48:11 +0400 [thread overview]
Message-ID: <4E959A9B.7060100@ru.mvista.com> (raw)
In-Reply-To: <CA+O4pCKMiLK3Z94j1NjVA3Zu-32X=tC-6eZnwGZCQXUTbhiEwA@mail.gmail.com>
On 10/12/2011 04:36 PM, Markus Rechberger wrote:
> We have 2 products which can perform better with increased Bulk transfers
> Device No. 1:
> According to the hardware spec of on of our product
> Available Bulk Transfer Size are:
> - 188 * n bytes, where n = 1 ~ 256.
> Although we can drive that one with 15K as well when setting the HW
> register down to it.
> Device No. 2
> only creates jitter video with Bulk transfer sizes which are below
> 24064 bytes, no such chipfeature is available
> to decrease the bulk transfer size.
> http://sundtek.de/images/dtvjitter2.jpg
> with transfer size of 24064:
> http://sundtek.de/images/gooddata.jpg
> The patch takes the features of Device No. 1 into account allowing a
> maximum buffer of 48128 bytes.
> Those issues have been evaluated with MacOSX and a customized patched
> Linux version.
> Device No. 2 also corrupts on MacOSX with too small packet sizes,
> Windows and Mac are using 24064 bytes.
You are constantly mixing the packet size and the transfer size.
> Default Bulk Transfersize of device No. 1 is around 1-2k which leads
> to very high cpu usage, updating it to 15k lowers that one.
WBR, Sergei
next prev parent reply other threads:[~2011-10-12 13:49 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 12:36 [Patch] Increase USBFS Bulk Transfer size Markus Rechberger
2011-10-12 12:46 ` Markus Rechberger
2011-10-12 13:48 ` Sergei Shtylyov [this message]
2011-10-12 14:17 ` Greg KH
2011-10-12 16:59 ` Markus Rechberger
2011-10-12 20:33 ` Greg KH
2011-10-12 21:48 ` Markus Rechberger
2011-10-12 22:09 ` Markus Rechberger
2011-10-13 4:03 ` Manu Abraham
2011-10-13 4:59 ` Markus Rechberger
2011-10-13 5:46 ` Manu Abraham
2011-10-13 8:37 ` Markus Rechberger
2011-10-13 9:29 ` Markus Rechberger
2011-10-16 9:22 ` James Courtier-Dutton
2011-10-13 9:34 ` Manu Abraham
2011-10-13 9:39 ` Markus Rechberger
2011-10-13 14:58 ` Alan Stern
2011-10-13 15:19 ` Markus Rechberger
2011-10-13 16:01 ` Chris Friesen
2011-10-13 16:12 ` Markus Rechberger
2011-10-13 16:25 ` Chris Friesen
2011-10-13 18:27 ` Markus Rechberger
2011-10-13 20:07 ` Alan Stern
2011-10-13 20:17 ` Markus Rechberger
2011-10-13 18:21 ` Alan Stern
2011-10-13 19:05 ` Alan Cox
2011-10-14 19:21 ` Johannes Stezenbach
2011-10-14 20:19 ` Alan Stern
2011-10-14 22:45 ` Johannes Stezenbach
2011-10-15 11:45 ` Markus Rechberger
2011-10-15 17:47 ` Valdis.Kletnieks
2011-10-15 19:08 ` Alan Stern
2011-10-15 19:04 ` Alan Stern
2011-10-16 9:10 ` Johannes Stezenbach
2011-10-16 14:18 ` Alan Stern
2011-10-17 18:11 ` Johannes Stezenbach
2011-10-17 18:22 ` Alan Stern
[not found] ` <CAAMvbhFNTQeuJBgsDB9Y5ODc_b2O0X=oP_3uwRpWUREFS9qufA@mail.gmail.com>
2011-10-14 2:47 ` Markus Rechberger
2011-10-14 3:42 ` Markus Rechberger
2011-10-14 3:48 ` Markus Rechberger
2011-10-14 5:47 ` Valdis.Kletnieks
2011-10-14 6:23 ` Markus Rechberger
2011-10-14 8:51 ` James Courtier-Dutton
2011-10-14 15:38 ` Markus Rechberger
2011-10-14 14:05 ` Alan Stern
2011-10-14 14:33 ` Greg KH
2011-11-07 18:52 ` Sarah Sharp
2011-11-07 19:12 ` Alan Stern
2011-11-07 20:18 ` Sarah Sharp
2011-11-07 20:37 ` Brink, Peter
2011-11-07 20:53 ` Alan Stern
2011-11-07 21:49 ` Greg KH
2011-11-07 23:07 ` Sarah Sharp
2011-11-08 1:44 ` Alan Stern
2011-11-07 19:16 ` Tim Vlaar
2011-11-07 19:55 ` Alan Stern
2011-11-07 20:13 ` Tim Vlaar
2011-10-17 18:38 ` Alan Stern
2011-10-17 19:07 ` Markus Rechberger
2011-10-12 18:00 ` Mihai Moldovan
2011-10-12 20:36 ` Greg KH
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=4E959A9B.7060100@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mrechberger@gmail.com \
--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 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.