From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756092Ab1JQOfq (ORCPT ); Mon, 17 Oct 2011 10:35:46 -0400 Received: from mga03.intel.com ([143.182.124.21]:56951 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756056Ab1JQOfo (ORCPT ); Mon, 17 Oct 2011 10:35:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.69,359,1315206000"; d="scan'208";a="63334394" Message-ID: <4E9C3D39.9020109@linux.intel.com> Date: Mon, 17 Oct 2011 07:35:37 -0700 From: Arjan van de Ven User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Peter Zijlstra CC: Matthew Garrett , Thomas Gleixner , Lennart Poettering , Andrew Morton , "Kirill A. Shutemov" , Paul Menage , Li Zefan , containers@lists.linux-foundation.org, jacob.jun.pan@linux.intel.com, linux-kernel@vger.kernel.org, Matt Helsley , linux-api@vger.kernel.org, Kay Sievers , harald@redhat.com, david@fubar.dk, greg@kroah.com Subject: Re: [PATCH, v10 3/3] cgroups: introduce timer slack controller References: <20111014154348.ae6267aa.akpm@linux-foundation.org> <20111015112006.GA10173@tango.0pointer.de> <1318705910.2664.5.camel@laptop> <20111017013921.GA30035@tango.0pointer.de> <20111017032232.GA4816@srcf.ucam.org> <4E9BBB6D.4050004@linux.intel.com> <1318837019.6594.29.camel@twins> <20111017124647.GA12838@srcf.ucam.org> <1318856786.4172.22.camel@twins> <20111017141147.GA14581@srcf.ucam.org> <1318861707.4172.32.camel@twins> In-Reply-To: <1318861707.4172.32.camel@twins> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/17/2011 7:28 AM, Peter Zijlstra wrote: > Or even when I minimize firefox. That said, ff will probably crash as > soon as I open a second tab because the retarded thing will very > likely continue animating everything on the invisible tab anyway. You > could start by making the X lib of the day, is that XCB these days?, > issue an error print (you get plenty of those anyway) and progress to > full on crashing later. This gives developers a migration window and > incentive to fix up their apps. so back in the time that worked on a project that used Qt as their toolkit (geez is it that long ago already ;-) )... we fixed Qt to stop doing this. The right level for this sort of thing is the toolkit level (which by and large also does the animations), not Xlib. The toolkit level also will then need to provide the right notifications to the app for things the toolkit does not do (eg "we're at least partially visible" versus "now none of our pixels are on the screen"). It ended up being a thing for the toolkit and a minor tweak in the compositor... and it worked quite ok, the app guys actually asked for the API (because they knew I would beat them up for getting it wrong)... doing things on the xlib level (or even X level) means you take away the chance for the App(tm) to do things the right way; make it easy for the app, not hard.