This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
RE: [PATCH] Native POSIX Thread Library(NPTL) ARMSupportingPatches (1/3)
- From: Philip Blundell <pb at nexus dot co dot uk>
- To: "Hu, Boris" <boris dot hu at intel dot com>
- Cc: "Libc-Alpha (E-mail)" <libc-alpha at sources dot redhat dot com>, "NPTL list (E-mail)" <phil-list at redhat dot com>
- Date: 30 May 2003 22:42:05 +0100
- Subject: RE: [PATCH] Native POSIX Thread Library(NPTL) ARMSupportingPatches (1/3)
- References: <37FBBA5F3A361C41AB7CE44558C3448E1A1844@pdsmsx403.ccr.corp.intel.com>
On Fri, 2003-05-30 at 09:05, Hu, Boris wrote:
> Here is the draft modication. Do I miss or misunderstand sth? If no,
> I could update the kernel & glibc patch. thanks.
Yup, that looks like what I had in mind. The only thing we need to
decide about is the multiprocessor case that Jakub mentioned. If we
need to support that, and it has to be done by dcache lockdown, it would
probably be best if the kernel got to choose the location of the thread
variable, rather than the application.
It might be worth asking the good folk on the linux-arm-kernel list for
their views. I suppose the other thing to do would be to try to collate
some benchmarks to find out how often threaded programs tend to call
THREAD_SELF(), so we can determine how much of a performance issue this
will actually be.
p.