On 21.12.2012 14:16, Fabian Keil wrote:
Fabian Keil <freebsd-lis...@fabiankeil.de> wrote:
Alexander Motin <m...@freebsd.org> wrote:
On 20.12.2012 15:26, Fabian Keil wrote:
Alexander Motin <m...@freebsd.org> wrote:
On 20.12.2012 12:56, Fabian Keil wrote:
Alexander Motin <m...@freebsd.org> wrote:
Experiments with dummynet shown ineffective support for very short
tick-based callouts. New version fixes that, allowing to get as many
tick-based callout events as hz value permits, while still be able to
aggregate events and generating minimum of interrupts.
Also this version modifies system load average calculation to fix some
cases existing in HEAD and 9 branches, that could be fixed with new
direct callout functionality.
http://people.freebsd.org/~mav/calloutng_12_17.patch
With this patch (and the previous one, I didn't test the others)
my mouse cursor is occasionally not reacting for short amounts of
time (less than a second, but long enough to be noticeable).
Could you try to revert part of the patch, related to dev/atkbdc? I am
not strong in details of that hardware, but in comments there mention
that they are related. May be lost keyboard interrupts (which polling
rate was increased to 1 second) cause PS/2 mouse delays.
I reverted the changes to sys/dev/atkbdc/* about an hour ago
and so far it's looking good. I'll report back tomorrow after
some more testing.
Still looking good.
Thank you. I think it may be some locking issue in atkbdc code. I'll
revert that part of the patch until somebody rewrite it properly.
--
Alexander Motin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
