mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	matt mooney <mfm@muteddisk.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-usb@vger.kernel.org, linux-uvc-devel@lists.berlios.de,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] USB: EHCI: Allow users to override 80% max periodic bandwidth
Date: Thu, 30 Jun 2011 11:01:01 -0700	[thread overview]
Message-ID: <20110630180101.GB7979@xanatos> (raw)
In-Reply-To: <cover.1308933456.git.kirr@mns.spb.ru>

On Fri, Jun 24, 2011 at 08:48:06PM +0400, Kirill Smelkov wrote:
> 
> Changes since v1:
> 
> 
>  - dropped RFC status as "this seems like the sort of feature somebody might
>    reasonably want to use -- if they know exactly what they're doing";
> 
>  - new preparatory patch (1/2) which moves already-in-there sysfs code into
>    ehci-sysfs.c;
> 
>  - moved uframe_periodic_max parameter from module option to sysfs attribute,
>    so that it can be set per controller and at runtime, added validity checks;
> 
>  - clarified a bit bandwith analysis for 96% max periodic setup as noticed by
>    Alan Stern;
> 
>  - clarified patch description saying that set in stone 80% max periodic is
>    specified by USB 2.0;

Have you tested this patch by maxing out this bandwidth on various
types of host controllers?  It's entirely possible that you'll run into
vendor-specific bugs if you try to pack the schedule with isochronous
transfers.  I don't think any hardware designer would seriously test or
validate their hardware with a schedule that is basically a violation of
the USB bus spec (more than 80% for periodic transfers).

But if Alan is fine with giving users a way to shoot themselves in the
foot, and it's disabled by default, then I don't particularly mind this
patch.

Sarah Sharp

  parent reply	other threads:[~2011-06-30 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 16:48 Kirill Smelkov
2011-06-24 16:48 ` [PATCH 1/2] USB: EHCI: Move sysfs related bits into ehci-sysfs.c Kirill Smelkov
2011-06-25 12:10   ` Alan Stern
2011-06-29  9:20     ` Kirill Smelkov
2011-06-29 15:23       ` Alan Stern
2011-06-29 16:40         ` Kirill Smelkov
2011-06-29 17:35           ` Alan Stern
2011-06-29 18:03             ` Kirill Smelkov
2011-06-29 18:51               ` Alan Stern
2011-07-01 11:49                 ` Kirill Smelkov
2011-07-01 15:41                   ` Alan Stern
2011-07-02 10:09                     ` Kirill Smelkov
2011-07-02 12:39                       ` Alan Stern
2011-07-03 16:39                         ` Kirill Smelkov
2011-06-24 16:48 ` [PATCH v2 2/2] USB: EHCI: Allow users to override 80% max periodic bandwidth Kirill Smelkov
2011-06-30 18:01 ` Sarah Sharp [this message]
2011-07-01  9:27   ` [PATCH v2 0/2] " Kirill Smelkov

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=20110630180101.GB7979@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=kirr@mns.spb.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-uvc-devel@lists.berlios.de \
    --cc=mfm@muteddisk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®