Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262882AbUCRSjS (ORCPT ); Thu, 18 Mar 2004 13:39:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262872AbUCRSip (ORCPT ); Thu, 18 Mar 2004 13:38:45 -0500 Received: from fw.osdl.org ([65.172.181.6]:41150 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262871AbUCRSeD (ORCPT ); Thu, 18 Mar 2004 13:34:03 -0500 Date: Thu, 18 Mar 2004 10:33:52 -0800 From: Andrew Morton To: Ingo Molnar Cc: torvalds@osdl.org, hch@infradead.org, drepper@redhat.com, linux-kernel@vger.kernel.org Subject: Re: sched_setaffinity usability Message-Id: <20040318103352.1a65126a.akpm@osdl.org> In-Reply-To: <20040318182407.GA1287@elte.hu> References: <40595842.5070708@redhat.com> <20040318112913.GA13981@elte.hu> <20040318120709.A27841@infradead.org> <20040318182407.GA1287@elte.hu> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 653 Lines: 14 Ingo Molnar wrote: > > Right now the VDSO mostly contains code and exception-handling data, but > it could contain real, userspace-visible data just as much: info that is > only known during the kernel build. There's basically no cost in adding > more fields to the VDSO, and it seems to be superior to any of the other > approaches. Is there any reason not to do it? It's x86-specific? - 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/