comp.programming.threads

• Thread Index

---

• Re: high performance thread communication (notification)
  • From: Rupert Kittinger
• Re: question about memory visibility on Windows
  • From: David Schwartz
• Re: What bad things happen if I do this with an array?
  • From: David Schwartz
• Re: What bad things happen if I do this with an array?
  • From: Francis Litterio
• Re: What bad things happen if I do this with an array?
  • From: MCD
• Re: Socket+3D - If client close, server close too
  • From: Raxit@xxxxxxxxxxxx
• Re: question about memory visibility on Windows
  • From: avik . ghosh
• Re: question about memory visibility on Windows
  • From: avik . ghosh
• Re: Double mutex lock vs Wait
  • From: David Schwartz
• Re: What bad things happen if I do this with an array?
  • From: David Schwartz
• Re: What bad things happen if I do this with an array?
  • From: Francis Litterio
• Re: What bad things happen if I do this with an array?
  • From: John Dallman
• What bad things happen if I do this with an array?
  • From: MCD
• Re: Double mutex lock vs Wait
  • From: Thomas Richter
• Re: Double mutex lock vs Wait
  • From: Szabolcs Ferenczi
• Re: Double mutex lock vs Wait
  • From: Thomas Richter
• Re: L'Equipe / Le Parisien
  • From: Juhani Björkman
• PDF FILES ABOUT HANI KALOUTI OR WORD FILES ABOUT HANI KALOUTI OR HTML ABOUT HANI KALOUTI
  • From: HANI KALOUTI FAN
• Re: Double mutex lock vs Wait
  • From: Szabolcs Ferenczi
• Re: Double mutex lock vs Wait
  • From: Thomas Richter
• Re: Double mutex lock vs Wait
  • From: Szabolcs Ferenczi
• Re: Double mutex lock vs Wait
  • From: Szabolcs Ferenczi
• Re: Double mutex lock vs Wait
  • From: danijel . korzinek
• Re: Double mutex lock vs Wait
  • From: Thomas Richter
• Re: Double mutex lock vs Wait
  • From: Eric Sosman
• Re: high performance thread communication (notification)
  • From: Thomas Richter
• high performance thread communication (notification)
  • From: wolfie2x
• Double mutex lock vs Wait
  • From: danijel . korzinek
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Alexander Terekhov
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Hallvard B Furuseth
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Friesen
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Thomas Richter
• Re: introducing faith/religion to kids
  • From: Heinonen
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Dave Butenhof
• Nukkumatti perkele
  • From: Markku Backman
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: How to use pthread_spin_lock() in RHEL AS 4
  • From: Chris Friesen
• Socket+3D - If client close, server close too
  • From: Mariano
• Re: How to use pthread_spin_lock() in RHEL AS 4
  • From: malc
• Re: How to use pthread_spin_lock() in RHEL AS 4
  • From: kbtrace
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Dave Butenhof
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Thomasson
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Thomasson
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: Chris Thomasson
• Re: Message Passing Idea
  • From: Chris Thomasson
• Re: Send message to all client.
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: How to use pthread_spin_lock() in RHEL AS 4
  • From: Natarajan Krishnaswami
• Re: Send message to all client.
  • From: Mariano
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Hallvard B Furuseth
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Dave Butenhof
• How to use pthread_spin_lock() in RHEL AS 4
  • From: msdaoz
• Re: Send message to all client.
  • From: Mariano
• Re: Send message to all client.
  • From: Mariano
• Re: Send message to all client.
  • From: Mariano
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Gil Hamilton
• Re: Send message to all client.
  • From: Mariano
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: Send message to all client.
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Dave Butenhof
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: Greg Herlihy
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: malc
• [C+Socket+Thread] Send message to all client.
  • From: Mariano
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: malc
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: malc
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: malc
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: Synchronizing with bool variables?
  • From: wolfie2x
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Anthony Williams
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: xtrigger303
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Anthony Williams
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: malc
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Friesen
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Alexander Terekhov
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Friesen
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Hallvard B Furuseth
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Chris Friesen
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Dave Butenhof
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: Which tools to find out why my program does not scale
  • From: ppi
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Anthony Williams
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: David Schwartz
• Re: PTHREAD_MUTEX_INITIALIZER
  • From: Anthony Williams
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: Ulrich Eckhardt
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: David Schwartz
• Re: Synchronizing with bool variables?
  • From: David Schwartz
• Re: Message Passing Idea
  • From: talmage . news
• Re: Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: Marcel Müller
• Re: Message Passing Idea
  • From: Chris Thomasson
• Re: Message Passing Idea
  • From: Chris Thomasson
• Re: Message Passing Idea
  • From: Chris Thomasson
• Re: Message Passing Idea
  • From: Chris Thomasson
• Re: Message Passing Idea
  • From: Chris Thomasson
• Win32: InterlockedExchange to write, InterlockedAdd(?) to read?
  • From: jason.cipriani@xxxxxxxxx
• Re: Message Passing Idea
  • From: Dmitriy V'jukov
• Re: Program crashes on rhel5 when pstack or gdb is invoked on it
  • From: Philip Guenther
• Re: Message Passing Idea
  • From: Dmitriy V'jukov
• Program crashes on rhel5 when pstack or gdb is invoked on it
  • From: Wind
• Re: Message Passing Idea
  • From: talmage . news
• Message Passing Idea
  • From: talmage . news
• Re: Synchronizing with bool variables?
  • From: Gerhard Fiedler
• Re: Synchronizing with bool variables?
  • From: Chris Thomasson
• Re: Synchronizing with bool variables?
  • From: Francis Litterio
• Re: Synchronizing with bool variables?
  • From: Francis Litterio
• Re: Are memory barriers needed on uniprocessor systems?
  • From: Peter Teoh
• Re: Synchronizing with bool variables?
  • From: David Schwartz
• Re: Synchronizing with bool variables?
  • From: Szabolcs Ferenczi
• Re: Synchronizing with bool variables?
  • From: Anthony Williams
• Re: Synchronizing with bool variables?
  • From: Gerhard Fiedler
• Re: Synchronizing with bool variables?
  • From: Szabolcs Ferenczi
• Synchronizing with bool variables?
  • From: Gerhard Fiedler
• Re: Which tools to find out why my program does not scale
  • From: Brian Cole
• Re: Which tools to find out why my program does not scale
  • From: David Schwartz
• Re: Which tools to find out why my program does not scale
  • From: scholz . lothar
• Re: Which tools to find out why my program does not scale
  • From: David Schwartz
• Which tools to find out why my program does not scale
  • From: scholz . lothar
• Re: Without pthread_exit
  • From: David Schwartz
• Re: Pthread programming: behavior of successive locks
  • From: David Schwartz
• Re: question about memory visibility on Windows
  • From: Torsten Robitzki
• Re: Without pthread_exit
  • From: Hallvard B Furuseth
• Re: Pthread programming: behavior of successive locks
  • From: Anthony Williams
• Pthread programming: behavior of successive locks
  • From: climber . cui
• Re: Without pthread_exit
  • From: jason.cipriani@xxxxxxxxx
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: David Schwartz
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: jason.cipriani@xxxxxxxxx
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: jason.cipriani@xxxxxxxxx
• Re: Differences between pthreads, windows threads and the new vista threads
  • From: jason.cipriani@xxxxxxxxx
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: David Schwartz
• Re: question about memory visibility on Windows
  • From: David Schwartz
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: jason.cipriani@xxxxxxxxx
• Re: Are memory barriers needed on uniprocessor systems?
  • From: Chris Friesen
• Differences between pthreads, windows threads and the new vista threads
  • From: Johan Torp
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: Ian Collins
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: jason.cipriani@xxxxxxxxx
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: Ian Collins
• linux, pthreads: yielding to another thread in realtime scheduled process on smp machine
  • From: jason.cipriani@xxxxxxxxx
• Re: Are memory barriers needed on uniprocessor systems?
  • From: David Schwartz
• Re: Are memory barriers needed on uniprocessor systems?
  • From: Francis Litterio
• Re: Are memory barriers needed on uniprocessor systems?
  • From: David Schwartz
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: David Schwartz
• Are memory barriers needed on uniprocessor systems?
  • From: Francis Litterio
• question about memory visibility on Windows
  • From: avik . ghosh
• WORK PART TIME GET $100 A WEEK CLICK HERE
  • From: PRINCE
• Re: Volatile reads/writes
  • From: Chris Thomasson
• Re: Code for Threading Models
  • From: Chris Thomasson
• Re: Volatile reads/writes
  • From: Chris Thomasson
• Re: Code for Threading Models
  • From: Steve Watt
• Volatile reads/writes
  • From: Dilip
• Re: To crash or not to crash.
  • From: Giancarlo Niccolai
• Re: To crash or not to crash.
  • From: Markus Elfring
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Wind
• To crash or not to crash.
  • From: Giancarlo Niccolai
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: David Schwartz
• Re: Without pthread_exit
  • From: Dave Butenhof
• Re: Without pthread_exit
  • From: Dave Butenhof
• Re: Without pthread_exit
  • From: Hallvard B Furuseth
• Re: Without pthread_exit
  • From: Anthony Williams
• Without pthread_exit
  • From: Peerless
• Re: Falcon threading module docs released.
  • From: Dave Butenhof
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Wind
• Re: Parallel multithreading for I/O operation in linux ?
  • From: Surinder Singh
• Parallel multithreading for I/O operation in linux ?
  • From: jurij
• Code for Threading Models
  • From: Lakshmi Narasu (a) Bujji
• Wanted - Software Developer - Bellevue, WA
  • From: stephbt
• Re: Are hazard pointers useful for wait-free programming?
  • From: Dmitriy V'jukov
• Re: Are hazard pointers useful for wait-free programming?
  • From: Johan Torp
• Re: Falcon threading module docs released.
  • From: Ian Collins
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Are hazard pointers useful for wait-free programming?
  • From: Anthony Williams
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• PERSONAL BANKRUPTCY
  • From: KALAIMANI
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Chris Thomasson
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Are hazard pointers useful for wait-free programming?
  • From: Chris Thomasson
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: David Schwartz
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Wind
• Are hazard pointers useful for wait-free programming?
  • From: Johan Torp
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: David Schwartz
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Igmar Palsenberg
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Wind
• Re: Pthread programming: about the lost condition signals.
  • From: Hallvard B Furuseth
• Re: ptrace fails with NPTL 2.5 on RHEL5
  • From: Igmar Palsenberg
• Re: Falcon threading module docs released.
  • From: Giancarlo Niccolai
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Falcon threading module docs released.
  • From: Giancarlo Niccolai
• ptrace fails with NPTL 2.5 on RHEL5
  • From: Wind
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Re: Falcon threading module docs released.
  • From: gc
• Re: Falcon threading module docs released.
  • From: Szabolcs Ferenczi
• Falcon threading module docs released.
  • From: Giancarlo Niccolai
• Re: Threading and/or Socket issues
  • From: Stuart
• Re: Only reading of variable vs. thread synchronisation
  • From: Surinder Singh
• Threading and/or Socket issues
  • From: bigdakine
• Re: Pthread programming: about the lost condition signals.
  • From: Surinder Singh
• Re: Pthread programming: about the lost condition signals.
  • From: Chris Thomasson
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Pthread programming: about the lost condition signals.
  • From: Sergei Organov
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: Ian Collins
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Only reading of variable vs. thread synchronisation
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Only reading of variable vs. thread synchronisation
  • From: Hapa
• Re: Pthread programming: about the lost condition signals.
  • From: Chris Thomasson
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Eric Sosman
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Alexander Terekhov
• Re: Only reading of variable vs. thread synchronisation
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Only reading of variable vs. thread synchronisation
  • From: sean_in_raleigh
• Re: Pthread programming: about the lost condition signals.
  • From: Eric Sosman
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Markus Elfring
• Re: Only reading of variable vs. thread synchronisation
  • From: Hapa
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Only reading of variable vs. thread synchronisation
  • From: Ian Collins
• Only reading of variable vs. thread synchronisation
  • From: Hapa
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• Re: Pthread programming: about the lost condition signals.
  • From: Chris Thomasson
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Szabolcs Ferenczi
• parallel computing - another conference, with proceedings
  • From: Richard Dobson
• Re: About synchronization methods
  • From: ppi
• Re: Pthread programming: about the lost condition signals.
  • From: Dave Butenhof
• Re: About synchronization methods
  • From: Dave Butenhof
• Re: Pthread programming: about the lost condition signals.
  • From: Chris Thomasson
• Re: Pthread programming: about the lost condition signals.
  • From: Eric Sosman
• Re: About synchronization methods
  • From: Chris Thomasson
• Re: About synchronization methods
  • From: Dave Butenhof
• Re: Atomically acquiring 32/64 spin-locks in single operation...
  • From: Chris Thomasson
• Re: About synchronization methods
  • From: Chris Thomasson
• Re: About synchronization methods
  • From: Szabolcs Ferenczi
• Re: About synchronization methods
  • From: Surinder Singh
• Re: About synchronization methods
  • From: Ian Collins
• Re: Pthread programming: about the lost condition signals.
  • From: Surinder Singh
• Re: About synchronization methods
  • From: Szabolcs Ferenczi
• Re: About synchronization methods
  • From: Chris Thomasson
• Re: About synchronization methods
  • From: Chris Thomasson
• Re: About synchronization methods
  • From: Ankur
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Steve Watt
• Re: Pthread programming: about the lost condition signals.
  • From: climber . cui
• Re: Pthread programming: about the lost condition signals.
  • From: David Schwartz
• Re: Pthread programming: about the lost condition signals.
  • From: Eric Sosman
• Pthread programming: about the lost condition signals.
  • From: climber . cui
• Re: About synchronization methods
  • From: Dave Butenhof
• Re: About synchronization methods
  • From: Szabolcs Ferenczi
• Re: About synchronization methods
  • From: Dave Butenhof
• Re: About synchronization methods
  • From: Szabolcs Ferenczi
• Re: About synchronization methods
  • From: Giancarlo Niccolai
• Re: About synchronization methods
  • From: Szabolcs Ferenczi
• Re: About synchronization methods
  • From: Dave Butenhof
• About synchronization methods
  • From: Ankur

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

newsgroups.derkeiler.com  > Archive  > Comp  > comp.programming.threads  > 2008-06