From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753510AbZHZUvz (ORCPT ); Wed, 26 Aug 2009 16:51:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753502AbZHZUvy (ORCPT ); Wed, 26 Aug 2009 16:51:54 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:49184 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753017AbZHZUvx (ORCPT ); Wed, 26 Aug 2009 16:51:53 -0400 Date: Wed, 26 Aug 2009 13:50:41 -0700 From: Andrew Morton To: Christoph Lameter Cc: mingo@elte.hu, peterz@infradead.org, raziebe@gmail.com, maximlevitsky@gmail.com, cfriesen@nortel.com, efault@gmx.de, riel@redhat.com, wiseman@macs.biu.ac.il, linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org Subject: Re: RFC: THE OFFLINE SCHEDULER Message-Id: <20090826135041.e6169d18.akpm@linux-foundation.org> In-Reply-To: References: <1251282598.3514.20.camel@raz> <1251297910.1791.22.camel@maxim-laptop> <1251298443.4791.7.camel@raz> <1251300625.18584.18.camel@twins> <1251302598.18584.31.camel@twins> <20090826180407.GA13632@elte.hu> <20090826193252.GA14721@elte.hu> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Aug 2009 16:40:09 -0400 (EDT) Christoph Lameter wrote: > Peter has not given a solution to the problem. Nor have you. What problem? All I've seen is "I want 100% access to a CPU". That's not a problem statement - it's an implementation. What is the problem statement? My take on these patches: the kernel gives userspace unmediated access to memory resources if it wants that. The kernel gives userspace unmediated access to IO devices if it wants that. But for some reason people freak out at the thought of providing unmediated access to CPU resources. Don't get all religious about this. If the change is clean, maintainable and useful then there's no reason to not merge it.