struct ieee80211_vif — per-interface data
struct ieee80211_vif {
enum nl80211_iftype type;
struct ieee80211_bss_conf bss_conf;
u8 addr[ETH_ALEN];
bool p2p;
bool csa_active;
u8 cab_queue;
u8 hw_queue[IEEE80211_NUM_ACS];
struct ieee80211_txq * txq;
struct ieee80211_chanctx_conf __rcu * chanctx_conf;
u32 driver_flags;
#ifdef CONFIG_MAC80211_DEBUGFS
struct dentry * debugfs_dir;
#endif
u8 drv_priv[0];
}; type of this virtual interface
BSS configuration for this interface, either our own or the BSS we're associated to
address of this interface
indicates whether this AP or STA interface is a p2p interface, i.e. a GO or p2p-sta respectively
marks whether a channel switch is going on. Internally it is write-protected by sdata_lock and local->mtx so holding either is fine for read access.
content-after-beacon (DTIM beacon really) queue, AP mode only
hardware queue for each AC
the multicast data TX queue (if driver uses the TXQ abstraction)
The channel context this interface is assigned to, or NULL
when it is not assigned. This pointer is RCU-protected due to the TX
path needing to access it; even though the netdev carrier will always
be off when it is NULL there can still be races and packets could be
processed after it switches back to NULL.
flags/capabilities the driver has for this interface, these need to be set (or cleared) when the interface is added or, if supported by the driver, the interface type is changed at runtime, mac80211 will never touch this field
debugfs dentry, can be used by drivers to create own per interface debug files. Note that it will be NULL for the virtual monitor interface (if that is requested.)
data area for driver use, will always be aligned to sizeof(void *).