linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, 20 Nov 2017 17:09:01 +0100	[thread overview]
Message-ID: <1511194141.2030.46.camel@sipsolutions.net> (raw)
In-Reply-To: <839c3938efae497e9058391fd4be4817@NALASEXR01H.na.qualcomm.com>

On Wed, 2017-11-15 at 19:21 +0000, Rajkumar Manoharan wrote:
> > 
> Hmm.. But polling TX/RX counters will not give exact activity time. 

Yeah but if you do it every minute, you'll know if it was idle for
roughly 5 minutes, or so... dunno, things could be done.

> Moreover
> It will be useful if STA's last data activity tstamp is logged in station dump. No?

I don't object to adding that, though we should be careful with adding
things and see if we _really_ need them, since they all have a cost.

johannes

      reply	other threads:[~2017-11-20 16:09 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
2017-11-15 19:21           ` Rajkumar Manoharan
2017-11-20 16:09             ` Johannes Berg [this message]

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