From: Artur Skawina <art.08.09@gmail.com>
To: Artur Skawina <art.08.09@gmail.com>
Cc: Christian Lamparter <chunkeey@web.de>,
linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [RFC][PATCH v2] p54usb: rx refill revamp
Date: Sat, 24 Jan 2009 21:56:47 +0100 [thread overview]
Message-ID: <497B808F.6060009@gmail.com> (raw)
In-Reply-To: <497B71E9.6080703@gmail.com>
Artur Skawina wrote:
> Christian Lamparter wrote:
>> On Saturday 24 January 2009 05:18:07 Artur Skawina wrote:
>>> [My version schedules the work for every urb, even the poisoned ones]
>> well, there's now a hard limit... no change of a endless loop now.
>
> The whole point of the poisoning was to prevent resubmission when
> canceling the urbs -- if you work around that manually, you could just
> as well kill them, instead of poisoning.
> I don't understand why want to add extra code to the rx irq just to
> avoid scheduling a work when downing the i/f, and keep a nasty failure
> case. The difference in down() performance is not going to be measurable,
> and even if it was, it wouldn't matter.
Oh, and we could always do something like
if (likely(atomic_read(&urb->reject)==0))
queue_work(priv->common.hw->workqueue, &priv->rx_refill_work);
which should catch most cases then urbs are either killed or poisoned.
artur
next prev parent reply other threads:[~2009-01-24 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 21:45 [RFC][PATCH v2] p54usb: rx refill revamp Christian Lamparter
2009-01-23 22:59 ` Artur Skawina
2009-01-24 1:15 ` Christian Lamparter
2009-01-24 4:18 ` Artur Skawina
2009-01-24 11:06 ` Christian Lamparter
2009-01-24 19:54 ` Artur Skawina
2009-01-24 20:56 ` Artur Skawina [this message]
2009-01-24 21:41 ` Artur Skawina
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=497B808F.6060009@gmail.com \
--to=art.08.09@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=linux-wireless@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.