Lines Matching refs:under

86 Device management under RTNL
94 Example flow of netdev handling under ``rtnl_lock``:
178 registration and de-registration, under ``rtnl_lock``. Drivers can use
179 those e.g. when parts of their init process need to run under ``rtnl_lock``.
262 	Context: atomic (can't sleep under RCU)
294 	``TC_SETUP_BLOCK`` and ``TC_SETUP_FT`` are running under NFT locks
296 	``tc_setup_type`` types run under netdev instance lock if the driver
300 under ``rtnl_lock``. In addition, netdev instance lock is taken as well if
326 operations will be performed under the netdev instance lock.
329 to drivers which have ops called under the instance lock as "ops locked".
334 operations directly under the netdev instance lock.
350 "Ops locked" drivers will have most of the ``ndos`` invoked under
358 be called under the instance lock.
363 "qstat" ops are invoked under the instance lock for "ops locked" drivers,
364 and under rtnl_lock for all other drivers.
387 some of the notifiers (``enum netdev_cmd``) are running under the netdev
390 The following netdev notifiers are always run under the instance lock:
394 running under the lock:
406 exceptions) notifiers run under the instance lock. Please extend this