From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/9] iwlagn: need longer tx queue stuck timer for coex devices
Date: Mon, 18 Oct 2010 07:16:47 -0700 [thread overview]
Message-ID: <1287411407.13051.39.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20101018121250.GA4005@redhat.com>
Hi Stanislaw,
On Mon, 2010-10-18 at 05:12 -0700, Stanislaw Gruszka wrote:
> Hi Wey
>
> > activity is too small time for device. Moreover we have unlikely but
> > possible situation when device is fully functional, but read_ptr will
> > wrap by accident to q->last_read_ptr on every check.
> >
> > I think, better solution would be something like in rt2x00 or in
> > net/sched/sch_generic.c (however rt2x00 is easier to understand). It is
> > based on time stamp. When we get tx complete notification from hardware
> > (and incise read_ptr) mark the time stamp. In watchdog, which tick
> > periodically, check if queue is not empty and if current time is
> > bigger than time_stamp + time_out, if it is - firmware hung. More
> > smaller watchog tick give more precise hung detect (with disadvantage
> > of more cpu usage).
> >
> >
> > Me too not really like the current "monitor" approach, some thought about the design you propose.
> >
> > 1. "time_out" is something need to be define and has the similar problem like what we have today since different devices has different behavior. For example, in WiFi/BT combo case, the queue might not move for a while if BT traffic load is high
>
> Sure.
>
> However new watchdog could be more precise. Currently if hung will
> happen just after watchdog tick we are detecting it in time about 2
> ticks i.e. 10s, or when happen just before the tick we detect the hang
> in 1 tick i.e. 5s, what gives 100% inaccuracy. New design can be much
> more precise.
>
> > 2. I don't really see much of "cpu usage" impact if we have a reasonable watchdog timer. But it is all relative.
>
> Ohh, I was talking about cpu usage in new design I described.
>
> >
> > By saying that, I think using timestamp might give more cleaner design, but still has the similar issues.
>
> Ok, if Intel have no plan to change the monitor recovery and have nothing
> against my watchdog approach, I'm going to cook some patches.
Pleas do so and please do let us review it. I am very happy having you
looking at the iwlwifi driver and give great improvement.
Thank you very much
Wey
next prev parent reply other threads:[~2010-10-18 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 18:02 [PATCH 0/9] update for 2.6.37 Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 1/9] iwlagn: need longer tx queue stuck timer for coex devices Wey-Yi Guy
2010-10-15 16:44 ` Stanislaw Gruszka
2010-10-15 18:01 ` Guy, Wey-Yi W
2010-10-18 12:12 ` Stanislaw Gruszka
2010-10-18 14:16 ` Guy, Wey-Yi [this message]
2010-10-14 18:02 ` [PATCH 2/9] iwlwifi: allow probe-after-rx on 2.4 GHz Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 3/9] iwlwifi: rename ibss_beacon variable Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 4/9] iwlwifi: clean up some beacon handling Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 5/9] iwlagn: 6050 ops should be used; Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 6/9] iwlwifi: rewrite RXON checks Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 7/9] iwlwifi: blink LED in IBSS mode Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 8/9] iwlagn: check beacon frame size Wey-Yi Guy
2010-10-14 18:02 ` [PATCH 9/9] iwlwifi: move agn only eeprom functions to separate file Wey-Yi Guy
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=1287411407.13051.39.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).