From: Johannes Berg <johannes@sipsolutions.net>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"rmanohar@codeaurora.org" <rmanohar@codeaurora.org>
Subject: Re: [PATCH] mac80211: Update last_ack status for all except probing frames
Date: Mon, 13 Nov 2017 10:25:41 +0100 [thread overview]
Message-ID: <1510565141.30497.6.camel@sipsolutions.net> (raw)
In-Reply-To: <96799d352b7347a8a9092bb37f1cd8d9@NALASEXR01H.na.qualcomm.com>
On Mon, 2017-11-06 at 20:20 +0000, Rajkumar Manoharan wrote:
> > > For steering an idle station from one BSS to another, the steering
> > > application has to know the actual station idle period. But if the
> > > idle period is cleared by ap_max_inactivity, the steering application
> > > cannot steer the station even though the station is not sending or receiving
> >
> > any data or mgmt. frame.
I guess you want something else. Why even consider a station that's
sending mgmt frames as non-idle?
You can just use the data TX/RX counters to figure out if the station
has been idle.
You've not convinced me that changing the current logic here makes any
sense.
johannes
next prev parent reply other threads:[~2017-11-13 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 0:29 [PATCH] mac80211: Update last_ack status for all except probing frames Rajkumar Manoharan
2017-11-01 2:31 ` Igor Mitsyanko
2017-11-02 18:06 ` Rajkumar Manoharan
2017-11-06 10:29 ` Johannes Berg
2017-11-06 17:44 ` Rajkumar Manoharan
2017-11-06 19:50 ` Igor Mitsyanko
2017-11-06 20:20 ` Rajkumar Manoharan
2017-11-13 9:25 ` Johannes Berg [this message]
2017-11-15 19:21 ` Rajkumar Manoharan
2017-11-20 16:09 ` Johannes Berg
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=1510565141.30497.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.qualcomm.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).