Date: Fri, 29 Jan 1999 13:50:23 -0500 (EST) From: HighWind Software Information <info@highwind.com> To: dick@tar.com Cc: dillon@apollo.backplane.com, current@FreeBSD.ORG Subject: Re: Locked at 100% User CPU Message-ID: <199901291850.NAA20468@highwind.com> In-Reply-To: <19990129092202.T421@tar.com> (dick@tar.com)
next in thread | previous in thread | raw e-mail | index | archive | help
> This code looks pretty bad, all right. It looks like it is O(N^2) > in PS_SELECT_WAIT(), especially if descriptors get randomly strewn > amoungst the threads. It also looks like it is regenerating the FDS masks > on each call completely from scratch. It also looks like it is > scanning the entire thread list - both waiting and running threads, > to prioritize the next thread to run and then scanning it again > to select the thread priority, then scanning the whole list yet > again to find the one it wants to run. > > This is massively unscaleable code. Is anyone actively working on > it? I think if I knew exactly what this code was trying to do, I could rewrite it. However, it is quite complex. I'm tempted to look into Richard's stuff. However, this pthread stuff is quite stable. (at least with a few minor tweaks). If this part scaled a WHOLE LOT better, we'd probably be okay. Richard: How "checked" in is your stuff? What does one have to do to start using it? Kernel mods? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901291850.NAA20468>