From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762733AbXGMCXh (ORCPT ); Thu, 12 Jul 2007 22:23:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757078AbXGMCXa (ORCPT ); Thu, 12 Jul 2007 22:23:30 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:4985 "EHLO scrub.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756587AbXGMCX3 (ORCPT ); Thu, 12 Jul 2007 22:23:29 -0400 Date: Fri, 13 Jul 2007 04:23:43 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Linus Torvalds cc: Andrea Arcangeli , Andi Kleen , Ingo Molnar , Andrew Morton , linux-kernel@vger.kernel.org, Thomas Gleixner , Arjan van de Ven , Chris Wright Subject: Re: x86 status was Re: -mm merge plans for 2.6.23 In-Reply-To: Message-ID: References: <20070710013152.ef2cd200.akpm@linux-foundation.org> <20070711174252.GA16793@elte.hu> <20070711211638.GE18767@one.firstfloor.org> <20070711214649.GK14435@v2.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, 11 Jul 2007, Linus Torvalds wrote: > Sure, bugs happen, but code that everybody runs the same generally doesn't > break. So a CPU scheduler doesn't worry me all that much. CPU schedulers > are "easy". A little more advance warning wouldn't have hurt though. The new scheduler does _a_lot_ of heavy 64 bit calculations without any attempt to scale that down a little... One can blame me now for not having it brought up earlier, but discussions with Ingo are not something I'm looking forward to. :( bye, Roman