From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753413AbXDRUIE (ORCPT ); Wed, 18 Apr 2007 16:08:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753512AbXDRUIE (ORCPT ); Wed, 18 Apr 2007 16:08:04 -0400 Received: from x35.xmailserver.org ([64.71.152.41]:3459 "EHLO x35.xmailserver.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753413AbXDRUIC (ORCPT ); Wed, 18 Apr 2007 16:08:02 -0400 X-AuthUser: davidel@xmailserver.org Date: Wed, 18 Apr 2007 13:07:59 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@alien.or.mcafeemobile.com To: Linus Torvalds cc: Ingo Molnar , Matt Mackall , Nick Piggin , William Lee Irwin III , Peter Williams , Mike Galbraith , Con Kolivas , ck list , Bill Huey , Linux Kernel Mailing List , Andrew Morton , Arjan van de Ven , Thomas Gleixner Subject: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] In-Reply-To: Message-ID: References: <20070417070155.GF1057@wotan.suse.de> <20070417213954.GE11166@waste.org> <20070418031511.GA18452@wotan.suse.de> <20070418043831.GR11115@waste.org> <20070418050024.GF18452@wotan.suse.de> <20070418055525.GS11115@waste.org> <20070418152355.GU11115@waste.org> <20070418174945.GA7930@elte.hu> <20070418175936.GA11980@elte.hu> X-GPG-FINGRPRINT: CFAE 5BEE FD36 F65E E640 56FE 0974 BF23 270F 474E X-GPG-PUBLIC_KEY: http://www.xmailserver.org/davidel.asc 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 On Wed, 18 Apr 2007, Linus Torvalds wrote: > For example, maybe we can approximate it by spreading out the statistics: > right now you have things like > > - last_ran, wait_runtime, sum_wait_runtime.. > > be per-thread things. Maybe some of those can be spread out, so that you > put a part of them in the "struct vm_struct" thing (to approximate > processes), part of them in the "struct user" struct (to approximate the > user-level thing), and part of it in a per-container thing for when/if we > support that kind of thing? I think Ingo's idea of a new sched_group to contain the generic parameters needed for the "key" calculation, works better than adding more fields to existing strctures (that would, of course, host pointers to it). Otherwise I can already the the struct_signal being the target for other unrelated fields :) - Davide