linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: linux-wireless@vger.kernel.org
Subject: [RFC PATCH 0/3] mac80211: nullfunc connection monitor
Date: Wed, 17 Feb 2010 23:04:01 +0200	[thread overview]
Message-ID: <20100217210202.30634.69236.stgit@tikku> (raw)

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


             reply	other threads:[~2010-02-17 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 21:04 Kalle Valo [this message]
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

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=20100217210202.30634.69236.stgit@tikku \
    --to=kalle.valo@iki.fi \
    --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 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).