Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755661AbZIVJU3 (ORCPT ); Tue, 22 Sep 2009 05:20:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755464AbZIVJU2 (ORCPT ); Tue, 22 Sep 2009 05:20:28 -0400 Received: from mail.gmx.net ([213.165.64.20]:56592 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755452AbZIVJU2 (ORCPT ); Tue, 22 Sep 2009 05:20:28 -0400 X-Authenticated: #14349625 X-Provags-ID: V01U2FsdGVkX1+3PENE1dq3tJ4W1QC/jvf7xeQ3ELnMD/pqGqOt/U yTeDMueT5u+KNB Subject: Re: Poor desktop responsiveness with background I/O-operations From: Mike Galbraith To: James Cloos Cc: lkml , Ulrich Lukas In-Reply-To: <1253603193.6875.118.camel@marge.simson.net> References: <4AB59CBB.8090907@datenparkplatz.de> <20090920080728.73bfe2a1@infradead.org> <4AB5ECD0.7010903@datenparkplatz.de> <1253475521.9224.43.camel@marge.simson.net> <4AB6C73C.1030004@gmail.com> <1253507034.23414.90.camel@marge.simson.net> <4AB72FDC.5090403@datenparkplatz.de> <1253520364.25640.57.camel@marge.simson.net> <1253603193.6875.118.camel@marge.simson.net> Content-Type: text/plain Date: Tue, 22 Sep 2009 11:20:28 +0200 Message-Id: <1253611228.11051.2.camel@marge.simson.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.7 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 632 Lines: 16 On Tue, 2009-09-22 at 09:06 +0200, Mike Galbraith wrote: > I don't know if distros provide a tool that supports SCHED_IDLE, if so, > you can use that to set both CPU and IO usage to IDLE class in one go. P.S. I just remembered, don't use SCHED_IDLE with kernels < 2.6.28. There are two patches wrt this scheduling class which did not go to the stable trees less than 2.6.28. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/