From owner-freebsd-current@FreeBSD.ORG Thu Dec 20 14:26:45 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 28644B18 for ; Thu, 20 Dec 2012 14:26:45 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bk0-f50.google.com (mail-bk0-f50.google.com [209.85.214.50]) by mx1.freebsd.org (Postfix) with ESMTP id 94CFD8FC0A for ; Thu, 20 Dec 2012 14:26:44 +0000 (UTC) Received: by mail-bk0-f50.google.com with SMTP id jf3so1719449bkc.37 for ; Thu, 20 Dec 2012 06:26:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4wFPZJlgZKWwWtG7MEJHH33h4CsItp8pMDx4LZzhVMw=; b=dQCDJ0S4ziw3MtBTBiQquXVMK3/mTNokDxiZ7H/2Sh2ZUQ9Sv3D96laf9uA9x828hh wmyJ6a4jHGiRElHFB9rRiOM+CsPfQOI5CHhmuwMOd36I+xecNMH90yyXUtBAZWGf45Yg qc3NfCxZLcKdEA1MbsEokgaPGjepjaZBzjyif7Qx9ftQRx10r3eTMAKf9h+2ooL4aM4F P0pmq4sfE9YqCBR4OlfVfeaoQBRxj8wPAAEjwnWCQ/7vZ2bSU2kKgCnSIt67RJUFBY0R 27m7f4ZJTcHEJO9VIW+V3LGhmZGIAKuADFW49NWoGf0Qi1GYb2DRJ2J/8VnpmhSkcyzk UMPQ== X-Received: by 10.204.128.197 with SMTP id l5mr4800655bks.59.1356013602954; Thu, 20 Dec 2012 06:26:42 -0800 (PST) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id y11sm7299221bkw.8.2012.12.20.06.26.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Dec 2012 06:26:41 -0800 (PST) Sender: Alexander Motin Message-ID: <50D3201F.4080605@FreeBSD.org> Date: Thu, 20 Dec 2012 16:26:39 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Fabian Keil Subject: Re: [RFC/RFT] calloutng 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> In-Reply-To: <20121220142600.22c4796a@fabiankeil.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2012 14:26:45 -0000 On 20.12.2012 15:26, Fabian Keil wrote: > Alexander Motin wrote: > >> On 20.12.2012 12:56, Fabian Keil wrote: >>> Alexander Motin 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). >>> >>> Every now and then the window manager (i3-wm) changes window focus >>> which could be explained by either phantom keyboard or mouse input, >>> or terminal lines are marked as if the cursor was moved with the >>> left button pressed. >>> >>> The problems happen a couple of times per hour but I haven't >>> been able to intentionally reproduce them. They only seem to >>> occur while I'm moving the cursor, but of course I wouldn't >>> otherwise notice a unresponsive cursor anyway. >>> >>> While the cursor is unresponsive, keyboard input and the rest >>> of the system works as expected as far as I can tell. >>> >>> If I set debug.psm.loglevel=4 I get a "psm0: lost interrupt?" >>> message once per second when not moving the mouse, however that >>> also happens without the patch and thus might be unrelated. >>> >>> I'm using moused. >> >> 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. Thank you for the report. If it will be fine. you can try to reapply that part of the patch, just changing line: callout_reset_flags(&sc->callout, hz, atkbdtimeout, dev, C_PRELSET(0)); to the: callout_reset_flags(&sc->callout, hz/10, atkbdtimeout, dev, C_PRELSET(0)); It should about to restore original polling interval, but still make it more flexible then original. -- Alexander Motin