linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH 0/3] mac80211: nullfunc connection monitor
@ 2010-02-17 21:04 Kalle Valo
  2010-02-17 21:04 ` [RFC PATCH 1/3] mac80211: refactor nullfunc status handling to a separate function Kalle Valo
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Kalle Valo @ 2010-02-17 21:04 UTC (permalink / raw)
  To: linux-wireless

I have been thinking about using nullfunc frames in connection monitor
with hw which have IEEE80211_HW_REPORTS_TX_ACK_STATUS. Here are my
current patches based on the idea. They have received minimal testing
and there's still some work to do.

But I would like to get comments what people think about this. Might
this create some kind of IOP problems, for example?

I also added a new hw flag to be able to offload connection monitoring
to the hardware.

TODO:

o send qos nullfunc when using wmm

---

Kalle Valo (3):
      mac80211: refactor nullfunc status handling to a separate function
      mac80211: use nullfunc in connection monitor
      mac80211: add support connection monitor in hardware


 include/net/mac80211.h     |    1 +
 net/mac80211/ieee80211_i.h |    1 +
 net/mac80211/mlme.c        |   40 +++++++++++++++++----
 net/mac80211/status.c      |   84 +++++++++++++++++++++++++++++++++++++-------
 4 files changed, 106 insertions(+), 20 deletions(-)


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-02-17 21:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-17 21:04 [RFC PATCH 0/3] mac80211: nullfunc connection monitor Kalle Valo
2010-02-17 21:04 ` [RFC PATCH 1/3] mac80211: refactor nullfunc status handling to a separate function Kalle Valo
2010-02-17 21:04 ` [RFC PATCH 2/3] mac80211: use nullfunc in connection monitor Kalle Valo
2010-02-17 21:04 ` [RFC PATCH 3/3] mac80211: add support connection monitor in hardware Kalle Valo

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).