Lines Matching +full:lookup +full:- +full:table

76 .Dq node table
87 Stations for all vaps reside in the same table; each node
95 Node table entries are reference counted.
98 References are held by every in-flight frame sent to a station to
101 Routines that lookup a table entry return a
103 (i.e. a pointer to a table entry with the reference count incremented).
109 reclaims the table entry.
111 The station table and its entries are exposed to drivers in several ways.
118 For each frame received the driver must lookup the table entry to
121 This lookup implicitly obtains a reference to the table entry and
128 The node table is opaque to drivers.
129 Entries may be looked up using one of the pre-defined API's or the
131 call may be used to iterate through all entries to do per-node
132 processing or implement some non-standard search mechanism.
135 is single-threaded per-device
144 displays the contents of the specified node table.
149 directive and the station node table can be displayed with
153 driver-private state.
156 method used to allocate a node table entry.
164 .Bd -literal -offset indent
172 .Bd -literal -offset indent
183 in->in_station = -1;
184 return &in->in_node;
193 .Bd -literal -offset indent
197 struct ieee80211com *ic = ni->ni_ic;
198 struct iwi_softc *sc = ic->ic_ifp->if_softc;
201 if (in->in_station != -1)
202 free_unr(sc->sc_unr, in->in_station);
203 sc->sc_node_free(ni); /* invoke net80211 free handler */
214 will not recognize this and table entries will not be reclaimed.
220 .Sh KEY TABLE SUPPORT
221 Node table lookups are typically done using a hash of the stations'
223 When receiving frames this is sufficient to find the node table entry
227 lookups on receive using a companion table called the
229 This table records a separate node table reference that can be fetched
230 without any locking using the table index.
234 returned directly; otherwise a normal lookup is done and the keytab
238 then a normal lookup is done without a table update.