public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Petter Selasky <hselasky@c2i.net>
To: "Amit Blay" <ablay@codeaurora.org>
Cc: "Sarah Sharp" <sarah.a.sharp@linux.intel.com>,
	"Tatyana Brokhman" <tlinder@codeaurora.org>,
	greg@kroah.com, linux-usb@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, balbi@ti.com,
	"Amit Blay" <ablay@qualcomm.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC 5/5] usb: Add support for streams alloc/dealloc to devio.c
Date: Mon, 22 Aug 2011 09:58:21 +0200	[thread overview]
Message-ID: <201108220958.21618.hselasky@c2i.net> (raw)
In-Reply-To: <7e62861a4ff90aa7990dda5563340797.squirrel@www.codeaurora.org>

On Sunday 21 August 2011 12:18:34 Amit Blay wrote:
> Thanks Sarah, Hans for your comments,
> 
> On Thu, August 18, 2011 3:47 pm, Sarah Sharp wrote:
> > Yes, I think this is the correct solution.  Sorry for taking so long to
> > get back to you.
> 
> OK, so I will go ahead with implementing this solution.
> 
> > On Wed, Aug 17, 2011 at 09:06:03AM +0200, Hans Petter Selasky wrote:
> >> I would suggest overloading the "unsigned int pipe", instead of breaking
> >> existing API's by adding a new stream ID value. Also for LibUSB.
> 
> The purposed solution will not break any existing API, by doing the
> following:
> a. Adding a new API for streams alloc/dealloc
> b. Adding a new API for submitting a URB which is stream capable (I will
> implement this in a separate patch).
> 
> > I don't see this as a strong argument why we should arbitrarily limit a
> > new API.  It's very hard to deprecate kernel to userspace API, so I
> > think we should do it right the first time.  There are current
> > applications (like an SSD behind a UAS device) that need as many
> > concurrent streams in flight as possible, so I don't buy the argument
> > that there aren't current applications that need that many streams.
> 
> I agree with Sarah.
> Hans, I appreciate your inputs. Please let me know if you see a good
> reason why not implementing the new APIs purposed above for streams
> allocation and usage. Otherwise I will go ahead with the implementation.

Hi Amit,

I think your suggestion is OK.

--HPS

  reply	other threads:[~2011-08-22  8:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 13:31 [PATCH/RFC 1/5] usb:tools: usb unittests framework Tatyana Brokhman
2011-06-16 13:31 ` [PATCH/RFC 2/5] usb:dummy_hcd: connect/disconnect test support Tatyana Brokhman
2011-06-16 15:06   ` Alan Stern
2011-06-16 16:16     ` Felipe Balbi
2011-06-16 17:06       ` Alan Stern
2011-06-16 17:19         ` Alan Stern
2011-06-16 15:17   ` Alan Stern
2011-06-16 16:18   ` Felipe Balbi
2011-06-16 13:31 ` [PATCH/RFC 3/5] usb:g_zero: bulk in/out unittest support Tatyana Brokhman
2011-06-16 16:25   ` Felipe Balbi
2011-06-16 13:31 ` [PATCH/RFC 4/5] usb:dummy_hcd: Disable single-request fifo in dummy hcd Tatyana Brokhman
2011-06-16 15:09   ` Alan Stern
2011-06-16 13:31 ` [PATCH/RFC 5/5] usb: Add support for streams alloc/dealloc to devio.c Tatyana Brokhman
2011-06-16 15:20   ` Alan Stern
2011-06-16 16:28   ` Felipe Balbi
2011-06-16 18:21     ` Greg KH
2011-06-17  8:55       ` ablay
2011-06-17 14:35         ` Alan Stern
2011-06-30 17:45   ` Sarah Sharp
2011-06-30 18:39     ` William Gulland
2011-06-30 18:41     ` Tanya Brokhman
2011-07-19  9:12     ` Amit Blay
2011-07-19  9:18       ` Oliver Neukum
2011-07-19 10:07         ` Amit Blay
2011-07-19 10:26           ` Oliver Neukum
2011-07-19 10:36             ` Amit Blay
2011-07-27  6:21       ` Amit Blay
2011-08-17  7:06         ` Hans Petter Selasky
2011-08-18 22:47         ` Sarah Sharp
2011-08-21 10:18           ` Amit Blay
2011-08-22  7:58             ` Hans Petter Selasky [this message]
2011-08-22  7:56           ` Hans Petter Selasky
2011-08-22 16:41             ` Sarah Sharp

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=201108220958.21618.hselasky@c2i.net \
    --to=hselasky@c2i.net \
    --cc=ablay@codeaurora.org \
    --cc=ablay@qualcomm.com \
    --cc=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=tlinder@codeaurora.org \
    /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