On Thu, 27 May 2010, Alexander Motin wrote:
Neel Natu wrote:
However it is not immediately obvious why we prefer to run the
statistics timer at (or very close to) 128Hz. Any pointers?
I haven't looked myself, but sources report that some legacy code depend
on it:
http://lists.freebsd.org/pipe
On Wed, 26 May 2010, Neel Natu wrote:
On Wed, May 26, 2010 at 8:20 PM, Alexander Motin wrote:
Neel Natu wrote:
Also, as soon as you run timer1 on frequency higher then hz - it is
strange to see
? ? ? ?stathz = hz;
? ? ? ?profhz = hz;
there. It is just useless. Better would be to do same as
Neel Natu wrote:
> However it is not immediately obvious why we prefer to run the
> statistics timer at (or very close to) 128Hz. Any pointers?
I haven't looked myself, but sources report that some legacy code depend
on it:
http://lists.freebsd.org/pipermail/freebsd-arch/2009-December/009731.html
Hi Alexander,
On Wed, May 26, 2010 at 8:20 PM, Alexander Motin wrote:
> Neel Natu wrote:
>> Author: neel
>> Date: Thu May 27 01:27:25 2010
>> New Revision: 208585
>> URL: http://svn.freebsd.org/changeset/base/208585
>>
>> Log:
>> Simplify clock interrupt handling on mips by using the new KPI -
Neel Natu wrote:
> Author: neel
> Date: Thu May 27 01:27:25 2010
> New Revision: 208585
> URL: http://svn.freebsd.org/changeset/base/208585
>
> Log:
> Simplify clock interrupt handling on mips by using the new KPI -
> timer1clock()
> and timer2clock().
>
> Dynamically adjust the tick fre
Author: neel
Date: Thu May 27 01:27:25 2010
New Revision: 208585
URL: http://svn.freebsd.org/changeset/base/208585
Log:
Simplify clock interrupt handling on mips by using the new KPI - timer1clock()
and timer2clock().
Dynamically adjust the tick frequency depending on the value of 'hz'. T
