From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [pgsql-www] NuSphere and PostgreSQL for windows |
Date: | 2003-09-25 15:53:10 |
Message-ID: | 87he30j255.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> writes:
> The little pthreads programming I did on linux/freeBSD tells me that it
> supports majority of features except TLS(linux2.4/linuxthreads) and per thread
> signals.
LinuxThreads is dead. NPTL is the way and the light.
It has ELF TLS which for super-fast thread-local storage, proper per-thread
signal semantics, as well as not using USR1,USR2 in ways that mess up
signal-handling. It also has kernel support for user-space mutexes (strange as
that may sound).
> >>I am sure local buffers would be lot cheaper than shared buffers.
> > On what do you base that? It sounds like pure fantasy to me. RAM is RAM.
Well that's not entirely true. Thread context switches don't involve MMU
operations the way process context switches do. So even though RAM is RAM, the
RAM in the threaded implementation might be faster to access simply because
it's already in the processor cache. The process model has to do a TLB flush
and load a whole new page table which takes a lot of time to begin with, and
then slows down all memory accesses later.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Spraul | 2003-09-25 16:03:00 | Re: [HACKERS] Threads vs Processes (was: NuSphere and PostgreSQL |
Previous Message | Robert Treat | 2003-09-25 15:36:52 | Re: PL contribution guidelines? |
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2003-09-25 17:01:38 | About developer.PostgreSQL.org redesign |
Previous Message | Greg Stark | 2003-09-25 15:18:51 | Re: [pgsql-www] NuSphere and PostgreSQL for windows |