Lines Matching refs:rtnl_lock

27 First group can be used in normal contexts where ``rtnl_lock`` is not already
29 Second group can be used when ``rtnl_lock`` is already held:
36 in context where ``rtnl_lock`` is not held (e.g. driver probe and remove paths).
90 the ``rtnl_lock`` requires extra care. In those scenarios most drivers
94 Example flow of netdev handling under ``rtnl_lock``:
155 ``rtnl_lock`` held.
168 happen after ``rtnl_lock`` is released, therefore in those cases free_netdev()
169 will defer some of the processing until ``rtnl_lock`` is released.
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``.
213 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
218 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
224 	Synchronization: rtnl_lock() semaphore.
231 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
239 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
247 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
255 	Synchronization: rtnl_lock() semaphore. In addition, netdev instance
295 	(i.e. no ``rtnl_lock`` and no device instance lock). The rest of
300 under ``rtnl_lock``. In addition, netdev instance lock is taken as well if
326 global lock known as ``rtnl_lock``. There is an ongoing effort to replace this
332 instance lock is acquired within the context of ``rtnl_lock``. The drivers
335 drivers to opt out of using ``rtnl_lock`` and instead perform their control