From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Date: Fri, 16 Jun 2006 15:40:18 +0000 Subject: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu() Message-Id: <200606161740.18611.ak@suse.de> List-Id: References: <200606140942.31150.ak@suse.de> <200606161656.40930.ak@suse.de> <20060616102516.A91827@pkunk.americas.sgi.com> In-Reply-To: <20060616102516.A91827@pkunk.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Brent Casavant Cc: Zoltan Menyhart , Jes Sorensen , Tony Luck , discuss@x86-64.org, linux-kernel@vger.kernel.org, libc-alpha@sourceware.org, vojtech@suse.cz, linux-ia64@vger.kernel.org > To this last point, it might be more reasonable to map in a page that > contained a new structure with a stable ABI, which mirrored some of > the task_struct information, and likely other useful information as > needs are identified in the future. In any case, it would be hard > to beat a single memory read for performance. That would mean making the context switch and possibly other things slower. In general you would need to make a very good case first that all this complexity is worth it. > Cache-coloring and kernel bookkeeping effects could be minimized if this > was provided as an mmaped page from a device driver, used only by > applications which care. I don't see what difference that would make. You would still have the fixed offset problem and doing things on demand often tends to be even more complex. -Andi (who thinks these proposals all sound very messy)