All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k ath_tx_complete_poll_work doesn't always run.
Date: Thu, 06 Jan 2011 11:55:14 -0800	[thread overview]
Message-ID: <4D261E22.1090300@candelatech.com> (raw)

It seems that the ath_tx_complete_poll_work method is supposed to
run every 1 second to check for stale xmit buffers.

However, I noticed that sometimes it is stopped, perhaps
because the mac80211 workqueue is flushed and ath9k
doesn't know to re-setup the work.

I am curious if anyone knows how this is *supposed* to
function?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: ath9k ath_tx_complete_poll_work doesn't always run.
Date: Thu, 06 Jan 2011 11:55:14 -0800	[thread overview]
Message-ID: <4D261E22.1090300@candelatech.com> (raw)

It seems that the ath_tx_complete_poll_work method is supposed to
run every 1 second to check for stale xmit buffers.

However, I noticed that sometimes it is stopped, perhaps
because the mac80211 workqueue is flushed and ath9k
doesn't know to re-setup the work.

I am curious if anyone knows how this is *supposed* to
function?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2011-01-06 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 19:55 Ben Greear [this message]
2011-01-06 19:55 ` ath9k ath_tx_complete_poll_work doesn't always run Ben Greear
2011-01-06 20:06 ` [ath9k-devel] " Ben Greear
2011-01-06 20:06   ` Ben Greear

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=4D261E22.1090300@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath9k-devel@lists.ath9k.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.