All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Felipe Tonello <eu@felipetonello.com>
Cc: USB list <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Peter Chen <Peter.Chen@freescale.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Felipe Balbi <balbi@ti.com>,
	Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Subject: Re: [PATCH v3 1/4] usb: gadget: f_midi: free usb request when done
Date: Mon, 12 Oct 2015 14:10:14 +0200	[thread overview]
Message-ID: <561BA326.7060209@ladisch.de> (raw)
In-Reply-To: <CAGrhNMyMbyojdsFoUcx6NVad5Amc5VXf41YPDmDckOwS5cug-g@mail.gmail.com>

Felipe Tonello wrote:
> On Mon, Oct 12, 2015 at 11:16 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
>> Felipe Tonello wrote:
>>> I believe that is the best way to implement. Create multiple requests
>>> until the ALSA substreams buffer are empty and free the request on
>>> completion.
>>
>> I believe a better way to implement this is to allocate a fixed number
>> of requests, and to always reuse them.
>
> How many?

Enough to get proper pipelining.  At least two, maybe not more.
(Depends on how fast those tiny CPUs can queue the next request.)

>>> The problem of having requests when host isn't listening will happen
>>> anyway because there is no way to know that until completion.
>>
>> But if you have no upper limit on the number of queues requests, you
>> will eventually run out of (DMA) memory.
>
> And that's what happening at the moment. One of my patches are to fix
> a memory leak when that happens.
>
> But it would be ideal to have a FIFO of requests and perhaps ignore
> new requests if the FIFO is full.
>
> So, allocate (pre-allocate?) new requests until the FIFO is full. Upon
> completion, remove the request from FIFO, but still reuse it on
> f_midi_transmit() and queue it on the FIFO again if there is still
> data from ALSA, otherwise just free the request.

Yes, that's exactly what I'm proposing.


Regards,
Clemens

      reply	other threads:[~2015-10-12 12:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 12:01 [PATCH v3 0/4] USB MIDI Gadget bug fixes and improvements Felipe F. Tonello
2015-09-29 12:01 ` [PATCH v3 1/4] usb: gadget: f_midi: free usb request when done Felipe F. Tonello
2015-09-29 12:01 ` [PATCH v3 2/4] usb: gadget: f_midi: free request when usb_ep_queue fails Felipe F. Tonello
2015-09-29 12:01 ` [PATCH v3 3/4] usb: gadget: f_midi: Transmit data only when IN ep is enabled Felipe F. Tonello
2015-09-29 12:01 ` [PATCH v3 4/4] usb: gadget: f_midi: remove duplicated code Felipe F. Tonello
2015-10-08  8:36 ` [PATCH v3 0/4] USB MIDI Gadget bug fixes and improvements Felipe Tonello
2015-10-09  9:23   ` [PATCH v3 1/4] usb: gadget: f_midi: free usb request when done Clemens Ladisch
2015-10-09 20:55     ` Felipe Balbi
2015-10-11 19:08       ` Clemens Ladisch
2015-10-12 10:11         ` Felipe Tonello
2015-10-12  9:46     ` Felipe Tonello
2015-10-12 10:16       ` Clemens Ladisch
2015-10-12 11:58         ` Felipe Tonello
2015-10-12 12:10           ` Clemens Ladisch [this message]

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=561BA326.7060209@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=Peter.Chen@freescale.com \
    --cc=andrzej.p@samsung.com \
    --cc=balbi@ti.com \
    --cc=eu@felipetonello.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 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.