SVNews r330451

NOTE: This service is experimental and subject to change! Use at your own risk!

2018-03-05 07:54:57 - r330451 by eadler (Eitan Adler)

Complete list of files affected by revision r330451:

(Note: At the moment, these links point to ViewVC on They are probably slow. Do not overuse.)

   Contents     MODIFY   /stable/11  
  History   Contents   Diff   MODIFY   /stable/11/sys/dev/iwm/if_iwm.c  
  History   Contents   Diff   MODIFY   /stable/11/sys/dev/otus/if_otus.c  
  History   Contents   Diff   MODIFY   /stable/11/sys/dev/usb/wlan/if_rsu.c  
  History   Contents   Diff   MODIFY   /stable/11/sys/net80211/ieee80211_freebsd.h  
  History   Contents   Diff   MODIFY   /stable/11/sys/net80211/ieee80211_input.c  

Commit message:

MFC r306837:

[net80211] extend the ieee80211_rx_stats struct to include more information.

There are a variety of more interesting RX statistics that we should
keep track of but we don't. This is a starting point for adding more


* now the RX rate information and some of the packet status is
  passed up;
* The 32 bit or 64 bit TSF is passed up;
* the PHY mode is passed up;
* the "I'm decap'ed AMSDU!" state is passed up;
* number of RX chains is bumped to 4.

This is all mostly a placeholder for getting the data into the RX status
before we pass it up to net80211 - unfortunately we don't yet enforce
that drivers provide it, nor do we pass the provided info back up the
stack so anyone can use the data.

We're going to need to use some of this data moving forward.
Notably, now that some hardware can do AMSDU decap for us (the intel iwm
driver can do it when we flip it on; the ath10k port I'm doing does
it for us) then we need to pass it up through the stack so the duplicate
RX sequence numbers and crypto/IV details don't cause the packet to
be dropped and/or counted against a replay counter.

It's also the beginning of being able to do more interesting node
accounting in net80211. Specifically, once drivers start populating
per-packet rate information, AMPDU information, timestamps, etc,
we can start providing histograms of rate-versus-RSSI, account
for receive time spent per node and other such interesting things.

(Note: I'm also hoping to include ranging and RTT information for
future chipset support; and it's likely going to include it in
this kind of fashion.)


Powered by Python FreeBSD support by secnetix GmbH & Co. KG

Page generated in 5 ms, 6 files printed. Current time is 2018-03-24 11:41:30. All times are in UTC/GMT.