[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180507155402.10086-1-pasha.tatashin@oracle.com>
Date: Mon, 7 May 2018 11:54:01 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: pasha.tatashin@...cle.com, steven.sistare@...cle.com,
daniel.m.jordan@...cle.com, linux-kernel@...r.kernel.org,
jeffrey.t.kirsher@...el.com, intel-wired-lan@...ts.osuosl.org,
netdev@...r.kernel.org, gregkh@...uxfoundation.org,
alexander.duyck@...il.com, tobin@...orbit.com
Subject: [PATCH v3 0/1] multi-threading device shutdown
Changelog
v2 - v3
- Fixed warning from kbuild test.
- Moved device_lock/device_unlock inside device_shutdown_tree().
v1 - v2
- It turns out we cannot lock more than MAX_LOCK_DEPTH by a single
thread. (By default this value is 48), and is used to detect
deadlocks. So, I re-wrote the code to only lock one devices per
thread instead of pre-locking all devices by the main thread.
- Addressed comments from Tobin C. Harding.
- As suggested by Alexander Duyck removed ixgbe changes. It can be
done as a separate work scaling RTNL mutex.
Do a faster shutdown by calling dev->*->shutdown(dev) in parallel.
device_shutdown() calls these functions for every single device but
only using one thread.
Since, nothing else is running on the machine by the device_shutdown()
s called, there is no reason not to utilize all the available CPU
resources.
Pavel Tatashin (1):
drivers core: multi-threading device shutdown
drivers/base/core.c | 275 ++++++++++++++++++++++++++++++++++++--------
1 file changed, 225 insertions(+), 50 deletions(-)
--
2.17.0
Powered by blists - more mailing lists