comp.programming.threads

• Thread Index

---

• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: Mayan Moudgill
• Re: pthread_mutex_trylock problem
  • From: AlterX
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• pthread_mutex_trylock problem
  • From: rajendra . stalekar
• pthreads in a static library
  • From: JimLasc
• Re: thread suspend using pthreads?
  • From: Joe Seigh
• Re: thread suspend using pthreads?
  • From: AlterX
• thread suspend using pthreads?
  • From: threadnewbie
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: LinuxThreads on 2.6 kernel
  • From: AlterX
• Re: Memory visibility and MS Interlocked instructions
  • From: Mayan Moudgill
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• LinuxThreads on 2.6 kernel
  • From: AKMarsh
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Seongbae Park
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Win32 condition variables redux
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: thread destructor ala atexit()
  • From: Frank Cusack
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: code profilers?
  • From: Markus Elfring
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: thread destructor ala atexit()
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• thread destructor ala atexit()
  • From: Frank Cusack
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Mayan Moudgill
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: code profilers?
  • From: Jacek Popławski
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Torsten Robitzki
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Torsten Robitzki
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Torsten Robitzki
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: Sean Kelly
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: code profilers?
  • From: Fred MacMurray
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: code profilers?
  • From: Randy
• Re: Memory visibility and MS Interlocked instructions
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Hopwood
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Chris Thomasson
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Luke Elliott
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Stack in thread-local virtual memory?
  • From: Jingbo
• Re: Stack in thread-local virtual memory?
  • From: Jingbo
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: code profilers?
  • From: Jacek Popławski
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Antw: thread safety
  • From: Alexander Fleck
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: code profilers?
  • From: Fred MacMurray
• Re: Memory visibility and MS Interlocked instructions
  • From: Scott Meyers
• Re: Memory visibility and MS Interlocked instructions
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Memory visibility and MS Interlocked instructions
  • From: Peter Dimov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: Scott Meyers
• Re: why my threads do not wake up
  • From: Jingbo
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: John Hickin
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: Alexander Terekhov
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Re: Memory visibility and MS Interlocked instructions
  • From: John Hickin
• Re: Memory visibility and MS Interlocked instructions
  • From: Scott Meyers
• Re: Memory visibility and MS Interlocked instructions
  • From: Joe Seigh
• Re: Memory visibility and MS Interlocked instructions
  • From: David Schwartz
• Memory visibility and MS Interlocked instructions
  • From: Scott Meyers
• Re: pthreads (linux) questions
  • From: Andrew Burgess
• Re: code profilers?
  • From: Paul Pluzhnikov
• Re: Can long blocking tasks scale?
  • From: Hans Malherbe
• Re: Can long blocking tasks scale?
  • From: Hans Malherbe
• Re: thread safety
  • From: Hung Nguyen
• Re: Can long blocking tasks scale?
  • From: Arnold Hendriks
• code profilers?
  • From: Jacek Popławski
• Re: Can long blocking tasks scale?
  • From: Hans Malherbe
• Re: why my threads do not wake up
  • From: roger . faulkner
• Re: thread safety
  • From: Missaka Wijekoon
• Re: why my threads do not wake up
  • From: David Schwartz
• Re: why my threads do not wake up
  • From: Jingbo
• Re: Can long blocking tasks scale?
  • From: robertwessel2@xxxxxxxxx
• Re: why my threads do not wake up
  • From: Jingbo
• Re: Can long blocking tasks scale?
  • From: Dave Vandervies
• Re: Can long blocking tasks scale?
  • From: Joe Seigh
• Can long blocking tasks scale?
  • From: Hans Malherbe
• Re: why my threads do not wake up
  • From: roger . faulkner
• Re: why my threads do not wake up
  • From: David Schwartz
• Re: why my threads do not wake up
  • From: Jingbo
• Re: nptl and signals
  • From: Joe Seigh
• Re: nptl and signals
  • From: divijbhatt@xxxxxxxxx
• Re: nptl and signals
  • From: Joe Seigh
• Re: _beginthread -- how to terminate a thread from out side of it.
  • From: Ian
• _beginthread -- how to terminate a thread from out side of it.
  • From: liangbowen
• Re: nptl and signals
  • From: divijbhatt@xxxxxxxxx
• Re: why my threads do not wake up
  • From: David Schwartz
• Re: why my threads do not wake up
  • From: Jingbo
• Re: nptl and signals
  • From: David Schwartz
• Re: nptl and signals
  • From: Loic Domaigne
• Re: PTHREAD SOURCE CODE
  • From: Duke Robillard
• Re: Paper - User-Level Threads for Hierarchically Composed Simulations
  • From: Mark Hodson
• Re: nptl and signals
  • From: divijbhatt@xxxxxxxxx
• Re: nptl and signals
  • From: Christian Parpart
• Re: nptl and signals
  • From: divijbhatt@xxxxxxxxx
• Re: Stack in thread-local virtual memory?
  • From: Ulrich Eckhardt
• Re: thread safety
  • From: Robben
• Re: Stack in thread-local virtual memory?
  • From: David Schwartz
• Re: Stack in thread-local virtual memory?
  • From: David Hopwood
• engineSMS SDK multithread per linux
  • From: AlterX
• Stack in thread-local virtual memory?
  • From: Ulrich Eckhardt
• Re: pthreads - cancellation
  • From: plinius
• Re: thread safety
  • From: Torsten Robitzki
• thread safety
  • From: Alexander Fleck
• Re: pthreads - cancellation
  • From: loic-dev
• Re: pthreads (linux) questions
  • From: David Schwartz
• Re: pthreads - cancellation
  • From: plinius
• Re: Paper - User-Level Threads for Hierarchically Composed Simulations
  • From: David Hopwood
• Re: pthreads (linux) questions
  • From: Christian Parpart
• Re: pthreads - cancellation
  • From: David Schwartz
• Re: Paper - User-Level Threads for Hierarchically Composed Simulations
  • From: Mark Hodson
• pthreads - cancellation
  • From: plinius
• Re: Using pthread in Windows
  • From: Fester
• Re: Killing threads
  • From: Fester
• Re: pthread and C++
  • From: Ian
• Re: pthreads (linux) questions
  • From: Joe Seigh
• Re: pthreads (linux) questions
  • From: jacob navia
• Re: pthreads (linux) questions
  • From: Joe Seigh
• Re: pthreads (linux) questions
  • From: jacob navia
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: chuckles
• Re: pthreads (linux) questions
  • From: Joe Seigh
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: Torsten Robitzki
• Re: exit_group: unfinished ... exit status 144
  • From: annamalai . gurusami
• Re: PTHREAD SOURCE CODE
  • From: Ian
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: loic-dev
• Re: exit_group: unfinished ... exit status 144
  • From: loic-dev
• Re: pthreads (linux) questions
  • From: jacob navia
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: loic-dev
• Re: NPTL and sigwait() problem under linux
  • From: loic-dev
• Re: pthreads (linux) questions
  • From: Joe Seigh
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: David Schwartz
• pthreads (linux) questions
  • From: jacob navia
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: chuckles
• Re: NPTL and sigwait() problem under linux
  • From: Steve Watt
• Re: Does pthread emit a sigchld signal on successful exit?
  • From: David Schwartz
• Does pthread emit a sigchld signal on successful exit?
  • From: chuckles
• RCU+SMR
  • From: Joe Seigh
• Re: PTHREAD SOURCE CODE
  • From: Phil Frisbie, Jr.
• Re: why my threads do not wake up
  • From: David Schwartz
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: annamalai . gurusami
• Re: why my threads do not wake up
  • From: Eric Sosman
• PTHREAD SOURCE CODE
  • From: Sean
• Re: NPTL and sigwait() problem under linux
  • From: Daniele
• why my threads do not wake up
  • From: Jingbo
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: Daniele
• Re: exit_group: unfinished ... exit status 144
  • From: annamalai . gurusami
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: loic-dev
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: Joe Seigh
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: annamalai . gurusami
• exit_group: unfinished ... exit status 144
  • From: annamalai . gurusami
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: Joe Seigh
• Re: atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: loic-dev
• atexit handler: pthread_cancel, pthread_testcancel, pthread_join problem
  • From: annamalai . gurusami
• Re: NPTL and sigwait() problem under linux
  • From: Loic Domaigne
• Re: NPTL and sigwait() problem under linux
  • From: Daniele
• Re: NPTL and sigwait() problem under linux
  • From: John Hickin
• Re: Killing threads
  • From: Giancarlo Niccolai
• Re: pthread_cond_timedwait problems
  • From: markh@xxxxxxxxxx
• Re: NPTL and sigwait() problem under linux
  • From: loic-dev
• Re: Killing threads
  • From: David Schwartz
• Re: Killing threads
  • From: David Hopwood
• Re: NPTL and sigwait() problem under linux
  • From: Daniele
• Re: Killing threads
  • From: David Schwartz
• Re: Killing threads
  • From: Phil Frisbie, Jr.
• Re: Killing threads
  • From: Ian
• Re: Killing threads
  • From: David Schwartz
• Re: Killing threads
  • From: Steve Watt
• Re: Killing threads
  • From: Joe Seigh
• Re: Killing threads
  • From: Srini Palthepu
• Re: Killing threads
  • From: Srini Palthepu
• Re: Killing threads
  • From: Srini Palthepu
• Re: Killing threads
  • From: Phil Frisbie, Jr.
• Re: Killing threads
  • From: David Schwartz
• Re: Formal Mutex Semantics
  • From: Joe Seigh
• Re: Killing threads
  • From: David Schwartz
• Re: Formal Mutex Semantics
  • From: Steve Watt
• Re: Formal Mutex Semantics
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Killing threads
  • From: Steve Watt
• Re: pthread_cond_timedwait problems
  • From: Steve Watt
• Killing threads
  • From: Srini Palthepu
• Killing threads
  • From: Srini Palthepu
• Re: Formal Mutex Semantics
  • From: John Hickin
• Re: Formal Mutex Semantics
  • From: Joe Seigh
• Re: NPTL and sigwait() problem under linux
  • From: John Hickin
• Re: Formal Mutex Semantics
  • From: John Hickin
• NPTL and sigwait() problem under linux
  • From: Daniele
• Re: Formal Mutex Semantics
  • From: Joe Seigh
• Re: Formal Mutex Semantics
  • From: Alexander Terekhov
• Re: Formal Mutex Semantics
  • From: Maciej Sobczak
• Re: Formal Mutex Semantics
  • From: Joe Seigh
• Using pthread in Windows
  • From: Thourda Huowaly
• Re: Formal Mutex Semantics
  • From: Maciej Sobczak
• Re: pthread_cond_timedwait problems
  • From: markh@xxxxxxxxxx
• Re: pthread_cond_timedwait problems
  • From: markh@xxxxxxxxxx
• Re: stupid threading question ....
  • From: Daniel Rayment
• Re: stupid threading question ....
  • From: Daniel Rayment
• Re: stupid threading question ....
  • From: David Schwartz
• Re: stupid threading question ....
  • From: David Hopwood
• Re: stupid threading question ....
  • From: John Hickin
• Re: Paper - User-Level Threads for Hierarchically Composed Simulations
  • From: David Hopwood
• Re: Proxy collector based on RCU+SMR hazard pointers
  • From: Joe Seigh
• Re: stupid threading question ....
  • From: David Schwartz
• Re: stupid threading question ....
  • From: John Hickin
• Re: stupid threading question ....
  • From: David Schwartz
• Paper - User-Level Threads for Hierarchically Composed Simulations
  • From: Mark Hodson
• Re: Memory visibility with Pthreads
  • From: Maciej Sobczak
• Re: stupid threading question ....
  • From: Daniel Rayment
• Re: stupid threading question ....
  • From: David Schwartz
• Re: stupid threading question ....
  • From: Paul Pluzhnikov
• Re: Proxy collector based on RCU+SMR hazard pointers
  • From: Joe Seigh
• stupid threading question ....
  • From: Daniel Rayment
• Re: Proxy collector based on RCU+SMR hazard pointers
  • From: d|dq
• Re: pthread_cond_timedwait problems
  • From: David Schwartz
• Re: pthreads and semaphore - Beginer question
  • From: plinius
• Proxy collector based on RCU+SMR hazard pointers
  • From: Joe Seigh
• Re: Formal Mutex Semantics
  • From: Joe Seigh
• Re: Memory visibility with Pthreads
  • From: Peter Dimov
• Re: pthread_cond_timedwait problems
  • From: Joe Seigh
• Re: pthread_cond_timedwait problems
  • From: markh@xxxxxxxxxx
• Re: pthread_cond_timedwait problems
  • From: David Schwartz
• Re: pthread_cond_timedwait problems
  • From: Ian
• Re: Formal Mutex Semantics
  • From: Chris Thomasson
• pthread_cond_timedwait problems
  • From: markh@xxxxxxxxxx
• Re: Formal Mutex Semantics
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Formal Mutex Semantics
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: Win32 condition variables & MySQL
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: Are Mutexes/Locks/Syncs necessary on a Read-only Array?
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: Win32 condition variables & MySQL
  • From: d|dq
• Are Mutexes/Locks/Syncs necessary on a Read-only Array?
  • From: KEN GUSTAFSON
• Re: posix and lock-free algorithms
  • From: Mayan Moudgill
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: Mayan Moudgill
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Sean Kelly
• Re: posix and lock-free algorithms
  • From: Sean Kelly
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Sean Kelly
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: Win32 condition variables & MySQL
  • From: Giancarlo Niccolai
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: A debugger/profiler not to interfere with threads ?
  • From: Jason Curl
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Programing dsPIC30F4011/dsPIC30F3011 and Schematic Automotive Injectors Driver
  • From: Dale Evans
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: How to guarantee no stale mutexes, ever?
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• How to guarantee no stale mutexes, ever?
  • From: Damon Hastings
• Re: A debugger/profiler not to interfere with threads ?
  • From: Timothy Madden
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: Memory visibility with Pthreads
  • From: Maciej Sobczak
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: A debugger/profiler not to interfere with threads ?
  • From: Jason Curl
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: Alexander Terekhov
• Re: posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: Memory visibility with Pthreads
  • From: Alexander Terekhov
• Re: Memory visibility with Pthreads
  • From: Maciej Sobczak
• Re: killing thread
  • From: Vitale Ferruccio
• Re: Memory visibility with Pthreads
  • From: Christoph Bartoschek
• Re: Memory visibility with Pthreads
  • From: David Schwartz
• Re: Memory visibility with Pthreads
  • From: Alexander Terekhov
• Re: Memory visibility with Pthreads
  • From: Alexander Terekhov
• Re: Memory visibility with Pthreads
  • From: David Schwartz
• Re: Memory visibility with Pthreads
  • From: Maciej Sobczak
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: killing thread
  • From: Patrick TJ McPhee
• Re: Memory visibility with Pthreads
  • From: David Schwartz
• Memory visibility with Pthreads
  • From: Christoph Bartoschek
• Re: killing thread
  • From: Alexander Terekhov
• Re: killing thread
  • From: Vitale Ferruccio
• Re: Win32 condition variables & MySQL
  • From: Ben Hutchings
• Re: killing thread
  • From: Joe Seigh
• Re: killing thread
  • From: Vitale Ferruccio
• Re: Win32 condition variables & MySQL
  • From: d|dq
• Re: Win32 condition variables & MySQL
  • From: d|dq
• Re: killing thread
  • From: Alexander Terekhov
• Re: killing thread
  • From: Alexander Terekhov
• Re: killing thread
  • From: Vitale Ferruccio
• A debugger/profiler not to interfere with threads ?
  • From: Timothy Madden
• Re: killing thread
  • From: David Butenhof
• Re: Win32 condition variables & MySQL
  • From: Alexander Terekhov
• Re: Can you limit the number of Posts to a POSIX semaphore?
  • From: Frank J. Lhota
• Re: Can you limit the number of Posts to a POSIX semaphore?
  • From: Frank J. Lhota
• Re: Win32 condition variables & MySQL
  • From: Joe Seigh
• killing thread
  • From: Vitale Ferruccio
• Re: Can you limit the number of Posts to a POSIX semaphore?
  • From: David Schwartz
• Re: Can you limit the number of Posts to a POSIX semaphore?
  • From: the_edge123 . nospam
• Re: posix and lock-free algorithms
  • From: David Holmes
• Win32 condition variables & MySQL
  • From: d|dq
• Re: threaded program and wait() call
  • From: tadek
• increasing the number of threads by reducing their stack size
  • From: emarinova
• Re: signaling threads from a forked child?
  • From: David Schwartz
• Re: signaling threads from a forked child?
  • From: Joe Seigh
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: Joe Seigh
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: thread log file
  • From: azb123
• Re: threaded program and wait() call
  • From: Patrick TJ McPhee
• Re: pthreads and semaphore - Beginer question
  • From: Fester
• thread log file
  • From: Jason Jesso
• Re: threaded program and wait() call
  • From: loic-dev
• Re: threaded program and wait() call
  • From: tadek
• Re: threaded program and wait() call
  • From: Patrick TJ McPhee
• Re: signaling threads from a forked child?
  • From: Patrick TJ McPhee
• Re: threads do not get cpa
  • From: Joe Seigh
• threads do not get cpa
  • From: azb123
• Re: Win32 condition variables redux
  • From: d|dq
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: pthreads and semaphore - Beginer question
  • From: David Schwartz
• Re: pthreads and semaphore - Beginer question
  • From: plinius
• Re: pthreads and semaphore - Beginer question
  • From: David Schwartz
• threaded program and wait() call
  • From: tadek
• Re: Win32 condition variables redux
  • From: d|dq
• Re: Win32 condition variables redux
  • From: d|dq
• Re: Win32 condition variables redux
  • From: Sean Kelly
• Re: workq: condvar vs semaphore
  • From: Sean Kelly
• Re: Win32 condition variables redux
  • From: d|dq
• Re: workq: condvar vs semaphore
  • From: Alexander Terekhov
• Re: workq: condvar vs semaphore
  • From: David Tiktin
• Re: workq: condvar vs semaphore
  • From: Alexander Terekhov
• workq: condvar vs semaphore
  • From: David Tiktin
• pthreads and semaphore - Beginer question
  • From: plinius
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: Win32 condition variables redux
  • From: Alexander Terekhov
• Re: signaling threads from a forked child?
  • From: Marcin 'Qrczak' Kowalczyk
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: Ben Hutchings
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: Joe Seigh
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: Patrick TJ McPhee
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Michael Pryhodko
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: signaling threads from a forked child?
  • From: Joe Seigh
• Re: Win32 condition variables redux
  • From: Charles Bryant
• Re: signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: signaling threads from a forked child?
  • From: Joe Seigh
• Can you limit the number of Posts to a POSIX semaphore?
  • From: Frank J. Lhota
• signaling threads from a forked child?
  • From: markh@xxxxxxxxxx
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: Sean Kelly
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Marcin 'Qrczak' Kowalczyk
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: How to change thread priority without being root
  • From: David Butenhof
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mayan Moudgill
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: d|dq
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: Joe Seigh
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: d|dq
• Re: Win32 condition variables redux
  • From: d|dq
• Re: Win32 condition variables redux
  • From: Charles Bryant
• Re: Win32 condition variables redux
  • From: Chris Thomasson
• Re: Win32 condition variables redux
  • From: Charles Bryant
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: Joe Seigh
• Re: Win32 condition variables redux
  • From: d|dq
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: d|dq
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: Joe Seigh
• Re: win32 threads broken (was Win32 condition variables redux)
  • From: d|dq
• win32 threads broken (was Win32 condition variables redux)
  • From: Joe Seigh
• Re: Win32 condition variables redux
  • From: Joe Seigh
• Win32 condition variables redux
  • From: d|dq
• Re: Adding thread support for C...
  • From: David Schwartz
• Re: Adding thread support for C...
  • From: Chris Friesen
• Re: pthread priority in Linux 2.4 Kernel
  • From: David Schwartz
• Re: Adding thread support for C...
  • From: David Schwartz
• Re: pthread priority in Linux 2.4 Kernel
  • From: David Schwartz
• Re: pthread priority in Linux 2.4 Kernel
  • From: David Hopwood
• Re: Adding thread support for C...
  • From: Charles Bryant
• Re: Adding thread support for C...
  • From: Chris Friesen
• Re: Adding thread support for C...
  • From: Marcin 'Qrczak' Kowalczyk
• Re: pthread priority in Linux 2.4 Kernel
  • From: David Schwartz
• Re: Adding thread support for C...
  • From: Charles Bryant
• Re: pthread priority in Linux 2.4 Kernel
  • From: David Schwartz
• Re: posix semaphores on AIX
  • From: Dragan Cvetkovic
• Re: Linux MultiTherad
  • From: David Schwartz
• Re: Linux MultiTherad
  • From: Joe Seigh
• Re: Linux MultiTherad
  • From: Gio67
• Re: Linux MultiTherad
  • From: AlterX
• Re: Linux MultiTherad
  • From: Gio67
• Re: posix and lock-free algorithms
  • From: Sean Kelly
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: posix and lock-free algorithms
  • From: David Hopwood
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: Linux MultiTherad
  • From: Joe Seigh
• Re: How to change thread priority without being root
  • From: yccheok
• Re: Linux MultiTherad
  • From: AlterX
• Linux MultiTherad
  • From: Gio67
• Re: How to change thread priority without being root
  • From: yccheok
• Re: posix and lock-free algorithms
  • From: peter . koch . larsen
• Re: How to change thread priority without being root
  • From: Ian
• Re: posix and lock-free algorithms
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• How to change thread priority without being root
  • From: yccheok
• Re: posix and lock-free algorithms
  • From: Joe Seigh
• posix and lock-free algorithms
  • From: John Doug Reynolds
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Peter Dimov
• Re: posix semaphores on AIX
  • From: Patrick TJ McPhee
• Re: QuickThreads
  • From: Paul Pluzhnikov
• QuickThreads
  • From: user2084
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Gianni Mariani
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Gianni Mariani
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Sean Kelly
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Peter Dimov
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Joe Seigh
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: David Schwartz
• Re: posix semaphores on AIX
  • From: The Gonzo Phaedrus
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Sean Kelly
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Chris Thomasson
• Re: posix semaphores on AIX
  • From: Steve Watt
• Re: posix semaphores on AIX
  • From: Dragan Cvetkovic
• Re: posix semaphores on AIX
  • From: David Jones
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: What is the real costs of LOCK on x86 multiprocesor machine?
  • From: chris noonan
• Re: posix semaphores on AIX
  • From: Dragan Cvetkovic
• What is the real costs of LOCK on x86 multiprocesor machine?
  • From: Mirek Fidler
• Re: implementing atomic<> on x86
  • From: Alexander Terekhov
• Re: posix semaphores on AIX
  • From: David Hopwood

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

newsgroups.derkeiler.com  > Archive  > Comp  > comp.programming.threads  > 2005-08