Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Dec 2012 14:49:16 +0200
From:      Alexander Motin <mav@FreeBSD.org>
To:        Fabian Keil <freebsd-listen@fabiankeil.de>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: [RFC/RFT] calloutng
Message-ID:  <50D45ACC.40608@FreeBSD.org>
In-Reply-To: <20121221131601.0d3ce382@fabiankeil.de>
References:  <50CCAB99.4040308@FreeBSD.org> <50CE5B54.3050905@FreeBSD.org> <50D03173.9080904@FreeBSD.org> <20121220115629.3379a261@fabiankeil.de> <50D2F923.2020303@FreeBSD.org> <20121220142600.22c4796a@fabiankeil.de> <50D3201F.4080605@FreeBSD.org> <20121220191243.7cd00b2a@fabiankeil.de> <20121221131601.0d3ce382@fabiankeil.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 21.12.2012 14:16, Fabian Keil wrote:
> Fabian Keil <freebsd-listen@fabiankeil.de> wrote:
>
>> Alexander Motin <mav@FreeBSD.org> wrote:
>>
>>> On 20.12.2012 15:26, Fabian Keil wrote:
>>>> Alexander Motin <mav@FreeBSD.org> wrote:
>>>>
>>>>> On 20.12.2012 12:56, Fabian Keil wrote:
>>>>>> Alexander Motin <mav@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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D45ACC.40608>