From: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
kvalo@codeaurora.org
Subject: Re: [PATCH v2] cfg80211/nl80211: Add support for NL80211_STA_INFO_RX_DURATION
Date: Wed, 9 Mar 2016 17:08:12 +0530 [thread overview]
Message-ID: <20160309113812.GA7581@atheros-ThinkPad-T61> (raw)
In-Reply-To: <1457522305.2042.3.camel@sipsolutions.net>
On Wed, Mar 09, 2016 at 12:18:25PM +0100, Johannes Berg wrote:
> On Wed, 2016-03-09 at 16:22 +0530, Mohammed Shafi Shajakhan wrote:
> >
> > [shafi] ath10k implementation is based on PPDU duration calculation
> > and it does not includes any IFS duration.
> >
> > So 'Energy' (time spent by the radio on receiving frames from a
> > particular peer) makes more sense right ?
> >
>
> Fine with me, perhaps just saying "aggregate PPDU duration" would be a
> good thing?
>
[shafi] thanks johannes, fine with me and I also confirmed with the person who
implemented this for ath10k, she is also fine with this definition as well.
I will send a v3 updating the same as below:
"@rx_duration: aggregate PPDU duration(usecs) for all the frames from a peer"
regards
shafi
next prev parent reply other threads:[~2016-03-09 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 7:20 [PATCH v2] cfg80211/nl80211: Add support for NL80211_STA_INFO_RX_DURATION Mohammed Shafi Shajakhan
2016-03-09 9:30 ` Johannes Berg
2016-03-09 9:38 ` Mohammed Shafi Shajakhan
2016-03-09 9:58 ` Johannes Berg
2016-03-09 10:52 ` Mohammed Shafi Shajakhan
2016-03-09 11:18 ` Johannes Berg
2016-03-09 11:38 ` Mohammed Shafi Shajakhan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-09 13:13 Mohammed Shafi Shajakhan
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=20160309113812.GA7581@atheros-ThinkPad-T61 \
--to=mohammed@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@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