Fix cpu hotplug atomic sleep issue
We move the spinlock unlock before the thread creation. This should be safe because the thread creation code doesn't actually manipulate any taskq data structures; that's done by the thread once it's created. We also remove the assertion that the maxthreads is the current threads plus one; that assertion could fail if multiple hotplug events come in quick succession, and the first new taskq thread hasn't had a chance to start processing yet. Reviewed-by:Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by:
Matthew Ahrens <mahrens@delphix.com> eviewed-by:
Tony Nguyen <tony.nguyen@delphix.com> Signed-off-by:
Paul Dagnelie <pcd@delphix.com> Closes #12714
Showing
+6 -5
Please register or sign in to comment