Bill Paul a50286e21d Make the multiple DPC threads an option, and create only one by default. ... This avoids the need for sched_bind() in the default case so that you can start up the NDIS subsystem at boot time when only CPU 0 is running. There are potentially ways to fix it so that the DPC threads aren't started until after the other CPUs are launched, but doing it correctly is tricky. You need to defer the startup of the ntoskrnl subsystem (ntoskrnl_libinit()), not just defer ndis_attach(). For now, I don't think it will make much difference having just the single DPC thread (I started out with just one anyway). Note that this turns the KeSetTargetProcessorDpc() routine into a no-op, since the CPU number in struct kdpc is now ignored.		2005-10-22 05:15:20 +00:00
..
freebsd32	regen after recvmsg, recvfrom, sendmsg	2005-10-15 05:57:34 +00:00
ia32	1. Change prototype of trapsignal and sendsig to use ksiginfo_t *, most	2005-10-14 12:43:47 +00:00
linprocfs	Always produce cpuX entries, even in the case when there is only one CPU	2005-03-06 22:28:14 +00:00
linux	1. Change prototype of trapsignal and sendsig to use ksiginfo_t *, most	2005-10-14 12:43:47 +00:00
ndis	Make the multiple DPC threads an option, and create only one by default.	2005-10-22 05:15:20 +00:00
netbsd	Start each of the license/copyright comments with /*-	2005-01-05 22:34:37 +00:00
pecoff	remove dead code	2005-02-22 01:26:48 +00:00
svr4	Fix compiling problem by adding prefix name svr4 to si_xxx macro, the	2005-10-19 09:33:15 +00:00