From owner-freebsd-current@FreeBSD.ORG Thu Dec 20 11:40:30 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 05227A45 for ; Thu, 20 Dec 2012 11:40:30 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bk0-f52.google.com (mail-bk0-f52.google.com [209.85.214.52]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB618FC14 for ; Thu, 20 Dec 2012 11:40:28 +0000 (UTC) Received: by mail-bk0-f52.google.com with SMTP id w5so1539698bku.25 for ; Thu, 20 Dec 2012 03:40:22 -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=m6PZPmLHops+iefzCen4FzWj9sRv42Ep9u6p4PMbMs4=; b=fqfYaBUh7baysfLpUfIhAjFSmQGtA3+xPWGiKrQqBB6FV21BHVaB99tHZ30ryUh416 atidA5C3yigCg8NX1vkTZfIb+Lgdg2ZiUZy5CwY0JVbMMuQH6JruNSDQI8hlUk/NXKMB wrQ3io2lbtmyWDm4/DaFZHHYKRQSczjKGlTtOwACFbfwrDXrUnoRjoiiFgkIYj8frqis W/0MOFCnk54UTEP9GMa2yXndNxJKp9q5tWbK34Om+cktOHLRCeApVsK97/D4kK2nxpJV AQS59wWkU8RiMqhVHJlcOh4ZuCX4wBP8wNoWSDuOBoAsqhR+NM4Va1x67mO8m82ULy4b N2tg== X-Received: by 10.204.128.148 with SMTP id k20mr4441239bks.107.1356003622378; Thu, 20 Dec 2012 03:40:22 -0800 (PST) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id i20sm6764739bkw.5.2012.12.20.03.40.20 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Dec 2012 03:40:21 -0800 (PST) Sender: Alexander Motin Message-ID: <50D2F923.2020303@FreeBSD.org> Date: Thu, 20 Dec 2012 13:40:19 +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> In-Reply-To: <20121220115629.3379a261@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 11:40:30 -0000 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. -- Alexander Motin