[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [PATCH] Native POSIX Thread Library(NPTL) ARM SupportingPatches(1/3)
- From: Dan Kegel <dank kegel com>
- To: "Hu, Boris" <boris hu intel com>
- Cc: Philip Blundell <pb nexus co uk>, Jakub Jelinek <jakub redhat com>, "Perez-Gonzalez, Inaky" <inaky perez-gonzalez intel com>, Daniel Jacobowitz <drow mvista com>, Wolfram Gloger <wmglo dent med uni-muenchen de>, "Libc-Alpha (E-mail)" <libc-alpha sources redhat com>, "NPTL list (E-mail)" <phil-list redhat com>
- Subject: Re: [PATCH] Native POSIX Thread Library(NPTL) ARM SupportingPatches(1/3)
- Date: Fri, 30 May 2003 08:46:11 -0700
I wonder what the performance impact is of having a system call in
THREAD_SELF. If it turns out to be too great, it may be possible to
reduce the overhead by adding some more support to the kernel. What
I've been thinking of is a way for applications to supply a pointer to
the kernel (via a new system call), and have it store the
current thread
ID at that address during context switch. That way, retrieving the
thread descriptor would be just a regular memory access.
This reminds me of vsyscalls. Can someone in the know compare and
contrast the current proposal and vsyscalls?
Thanks!
- Dan
p.s. Here's a recent message from around the time they switched
the vsyscall page from something created specially by the kernel
to a tiny ELF image:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105123323202704&w=2
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]