From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: channel utilisation short/long hdr?
Date: Sat, 12 Jan 2008 11:15:00 +0100 [thread overview]
Message-ID: <1200132900.3528.22.camel@johannes.berg> (raw)
In-Reply-To: <20080112024400.GC12245@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
> Hmm.. I thought I had filtered out the channel use estimation code from
> the original release since I did not see much use for this and the
> values were not exactly valid in many cases.. ;-).
Heh.
> This code is almost five years old and maybe not so surprisingly, I
> don't remember the exact details anymore.. Since these are use as
> "hdrtime", I would assume they were derived using following calculation:
Right. Thanks for the values, I guess that if we really wanted to keep
that stuff maintainable we should rewrite it and take into account
preamble length too etc. I'm not too keen on that though, would anybody
object if we'd just kill it?
> That would be any rate using Extended Rate PHY (ERP; 802.11 Clause 19).
> This is not necessarily OFDM (it could also be using PBCC modulation).
> In practice, I would expect the kernel side implementation to use this
> in anything PHY related as ERP-OFDM (i.e., it may not support optional
> PBCC rates). The association and beacon/probe processing may be more
> generic to any ERP rate. I don't think ERP-PBCC is very commonly used,
> so this may be more on the theoretical side..
Oh, right, I keep forgetting about the optional rates.
Thanks,
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-01-12 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 23:50 channel utilisation short/long hdr? Johannes Berg
2008-01-12 2:44 ` Jouni Malinen
2008-01-12 10:15 ` 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=1200132900.3528.22.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=flamingice@sourmilk.net \
--cc=j@w1.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