Date: Thu, 14 Oct 1999 00:34:28 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: mjacob@feral.com Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha clock.c interrupt.c Message-ID: <14341.23028.588066.932812@grasshopper.cs.duke.edu> In-Reply-To: <Pine.BSF.4.05.9910132106150.4344-100000@semuta.feral.com> References: <14341.18732.575731.734319@grasshopper.cs.duke.edu> <Pine.BSF.4.05.9910132106150.4344-100000@semuta.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Jacob writes: > > Rawhide: > > kern.clockrate: tick = 833, tickadj = 40, hz = 1200, profhz = 1200, stathz = 1200 <...> > > Insofar as what clock.c/interrupt.c shows- I'll plead ignorance! I haven't > fooled with schedulers since v7 days. I'd have to spend some time on it to > try and understand what is or isn't being assumed. > > Yes- I saw your example- All I was leaping in here on was the 'hz = 1024' > statement. Well, when FreeBSD runs on it, we'll worry about it ;-) But seriously, all I'm doing is part of what NetBSD is doing right now. I don't really know anything about the scheduler either. All I know is that reducing the frequency of calls to statclock dramitically improves scheduling. I think your example of a non 1024 hz just means we'll have to get statclock via hz/8 rather than hardcoding it to 128 (as NetBSD hardcodes it to 16..). I think all this could go away if the scheduler was fixed, but I'm not up to that task. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14341.23028.588066.932812>