From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: libertas-dev@lists.infradead.org
Cc: David Woodhouse <dwmw2@redhat.com>,
Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] libertas: reduce command retry time
Date: Thu, 1 May 2008 23:30:57 +0200 [thread overview]
Message-ID: <200805012330.57750.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1209588196.25560.443.camel@pmac.infradead.org>
> I think I've seen it take a few of the 5-second timeouts.
Do you you know for which commands this has been?
> I wouldn't like to decrease the maximum so drastically.
How far would you go?
Or: maybe there is another way to make "pccardctl eject"
work reasonably fast in the case of a retrying command. Any
idea?
BTW, it's easy to force this kind of error, in cmdresp.c:
if (resp->seqnum==5) {
lbs_deb_cmd("forced FAIL\n");
spin_unlock_irqrestore(&priv->driver_lock, flags);
ret = -1;
goto out;
}
> Also, that del_timer_sync() happens in the module unload path, doesn't
> it? I'd want to see why you think it isn't needed.
I thought that del_timer_sync() waits until the timer has been executed? If yes, then that's the wrong thing here, I want to unload quickly. Makes no sense to wait till the command_timer finally fires and re-sends the failed command.
next prev parent reply other threads:[~2008-05-01 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 14:44 [PATCH] libertas: reduce command retry time Holger Schurig
2008-04-30 20:34 ` Dan Williams
2008-04-30 20:43 ` David Woodhouse
2008-05-01 21:30 ` Holger Schurig [this message]
2008-05-01 21:57 ` David Woodhouse
2008-05-02 6:07 ` Holger Schurig
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=200805012330.57750.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=dwmw2@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.