> So to get a list of which clocksources your hardware has > available: > ># cat /sys/devices/system/clocksource/clocksource0/current_clocksource
I think you meant available_clocksource not current_clocksource ? > -----Original Message----- > From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux- > boun...@list.valvesoftware.com] On Behalf Of Gary Stanley > Sent: 07 March 2009 18:40 > To: Half-Life dedicated Linux server mailing list; Half-Life dedicated > Linux server mailing list > Subject: Re: [hlds_linux] Kernel Options and Clocksource > > At 01:12 PM 3/7/2009, Ben B wrote: > >dont ask me, this is how it was when i found it. So if I compile my > own > >kernel, it should have them clocksources? > > What's the motherboard? is it a virtual machine? > > > >On Sat, Mar 7, 2009 at 11:01 AM, Gary Stanley > ><g...@velocity-servers.net>wrote: > > > > > At 12:47 PM 3/7/2009, Ben B wrote: > > > >i just have jiffies in as an available clocksource... there a way > to get > > > >htpet and tsc? > > > > > > TSC should be always be available as a clocksource, unless > something > > > is seriously wrong with your setup. > > > Actually, a normal kernel will panic if TSC isn't compiled into the > kernel > > > :P > > > > > > > > > > > > >On Sat, Mar 7, 2009 at 8:34 AM, Gary Stanley <g...@velocity- > servers.net > > > >wrote: > > > > > > > > > At 08:27 AM 3/7/2009, listac...@lvwnet.com wrote: > > > > > > > I feel like such a linux nub... how do you set your > clocksource? > > > > > > > > > > > >On any fairly recent 2.6-series kernel you can put this right > on the > > > > > >kernel boot commandline: > > > > > > > > > > > >clocksource=$whatever > > > > > > > > > > > >like > > > > > > > > > > > >clocksource=hpet > > > > > > > > > > > >or > > > > > > > > > > > >clocksource=tsc > > > > > > > > > > > >so that it is set at boot. > > > > > > > > > > > >The echoing of available options into the /sys entry is valid > as well, > > > ie: > > > > > > > > > > > ># echo "hpet" > > > > > > > >/sys/devices/system/clocksource/clocksource0/current_clocksource > > > > > > > > > > > >but is more of a post-boot type thing. That's not bad, > necessarily. > > > You > > > > > >can use it to change the clocksource post-boot. This is > useful if you > > > are > > > > > >experimenting with different ones because you can change the > > > clocksource > > > > > >without rebooting. > > > > > > > > > > > >So to get a list of which clocksources your hardware has > available: > > > > > > > > > > > ># cat > /sys/devices/system/clocksource/clocksource0/current_clocksource > > > > > > > > > > > >you'll get something like this back (but it will vary from > system to > > > > > system): > > > > > > > > > > > >tsc jiffies hpet acpi_pm > > > > > > > > > > > > > > > > > > > > > > > >Someone else asked whether running a 500Hz timer resolution > will allow > > > you > > > > > >to get a stable 500 server fps. I'm not going to say it is > > > impossible, > > > > > >but I will say that *I* have yet to find a server machine > > > (server-class > > > > > >hardware) that would let me get 500fps with a 500Hz kernel. > > > > > > > > > > I was able to get it running on a test machine. > > > > > > > > > > >I've only ever been able to get 500 server fps with a 1000Hz > or > > > tickless > > > > > >kernel, and setting fps_max to 600 or higher. > > > > > > > > > > > >Entirely possible I'm just not doing it right though. But > what I do > > > > > >works, so I keep doing it. :) > > > > > > > > > > > >Setting fps_max to 600 usually gets me around 490-496 server > fps. CPU > > > > > >utilization for the core a full 30-slot server runs on is > usually > > > around > > > > > >60-65% on a 2.5GHz Harpertown but it does briefly peak higher > at > > > times. > > > > > > > > > > > >This is under F10 x86_64 with a stock 2.6.27 kernel (which I'm > pretty > > > sure > > > > > >is built dynamic/tickless) and I can get ~1000 server fps out > of it > > > for > > > > > >our CS:S games by setting fps_max to 2000. I'm using > clocksource=hpet > > > > > >currently, but have considered experimenting with tsc since > I've read > > > that > > > > > >there are some recent userspace optimizations in glibc for it > on > > > x86_64 > > > > > >which may be of benefit. > > > > > > > > > > That only happens if the binaries are x86_64. > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > To unsubscribe, edit your list preferences, or view the list > archives, > > > > > please visit: > > > > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > > > > > > > > > > > > >-- > > > > From Ben B. (Goerge) > > > >_______________________________________________ > > > >To unsubscribe, edit your list preferences, or view the list > > > >archives, please visit: > > > >http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > _______________________________________________ > > > To unsubscribe, edit your list preferences, or view the list > archives, > > > please visit: > > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > > >-- > > From Ben B. (Goerge) > >_______________________________________________ > >To unsubscribe, edit your list preferences, or view the list > >archives, please visit: > >http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux