mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: David VomLehn <dvomlehn@cisco.com>, linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, greg@kroah.com
Subject: Re: [PATCH 1/1, v2] usb-use-kfifo-to-buffer-usb-generic-serial-writes.patch
Date: Thu, 27 Aug 2009 10:14:53 +0200	[thread overview]
Message-ID: <200908271014.54282.oliver@neukum.org> (raw)
In-Reply-To: <20090827013454.GA23601@cuplxvomd02.corp.sa.net>


> +	/* send the data out the bulk port */
> +	result = usb_submit_urb(port->write_urb, GFP_ATOMIC);
> +	if (result) {
> +		dev_err(&port->dev,
> +			"%s - failed submitting write urb, error %d\n",
> +						__func__, result);
> +		/* don't have to grab the lock here, as we will
> +		   retry if != 0 */
> +		port->write_urb_busy = 0;
> +		status = result;

This looks deficient. If the first part of a transmission fails,
the fifo's remaining content should be discarded and if possible
an error returned to user space.

[..]
> @@ -487,8 +515,8 @@ void usb_serial_generic_write_bulk_callback(struct urb
> *urb) port->urbs_in_flight = 0;
>  		spin_unlock_irqrestore(&port->lock, flags);
>  	} else {
> -		/* Handle the case for single urb mode */
>  		port->write_urb_busy = 0;
> +		usb_serial_generic_write_start(port, 0);

This is a problem. This may fail due to a system suspend.
In that case you cannot depend on the next write restarting
IO. You need to restart IO in resume()


> @@ -970,6 +971,11 @@ int usb_serial_probe(struct usb_interface *interface,
>  			dev_err(&interface->dev, "No free urbs available\n");
>  			goto probe_error;
>  		}
> +		port->write_fifo = kfifo_alloc(PAGE_SIZE, GFP_KERNEL,
> +			&port->write_fifo_lock);

Whence do you take the fifo's size? What does this do to latency?

[..]
> @@ -96,6 +98,8 @@ struct usb_serial_port {
>  	unsigned char		*bulk_out_buffer;
>  	int			bulk_out_size;
>  	struct urb		*write_urb;
> +	struct kfifo		*write_fifo;
> +	spinlock_t		write_fifo_lock;

Do you really need a separate lock?

	Regards
		Oliver


  reply	other threads:[~2009-08-27  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  1:34 David VomLehn
2009-08-27  8:14 ` Oliver Neukum [this message]
2009-08-27 17:22   ` David VomLehn
2009-08-28 13:07     ` Oliver Neukum
2009-08-28 19:48       ` David VomLehn
2009-08-28 20:01         ` Alan Cox
2009-08-29 12:56           ` Oliver Neukum

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=200908271014.54282.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=akpm@linux-foundation.org \
    --cc=dvomlehn@cisco.com \
    --cc=greg@kroah.com \
    --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 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®