comp.programming.threads

• Thread Index

---

• Re: Rendering and physics thread repartition(scheduling?)
  • From: David Schwartz
• Re: Help me regarding hybrid threads
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Rendering and physics thread repartition(scheduling?)
  • From: Marcus Gambit
• Re: Rendering and physics thread repartition(scheduling?)
  • From: Chris Friesen
• Re: Cnet: "Intel: Optimize applications for multicore"
  • From: Chris Friesen
• Help me regarding hybrid threads
  • From: suresh . kandukuru
• Re: How to gracefully (programmatically) kill an app?
  • From: Eric Sosman
• Rendering and physics thread repartition(scheduling?)
  • From: Marcus Gambit
• How to gracefully (programmatically) kill an app?
  • From: durga
• Re: Cnet: "Intel: Optimize applications for multicore"
  • From: David Schwartz
• Re: Cnet: "Intel: Optimize applications for multicore"
  • From: Chris Thomasson
• Re: Cnet: "Intel: Optimize applications for multicore"
  • From: Joe Seigh
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: "Intel: Optimize applications for multicore"
  • From: Chris Thomasson
• Cnet: "Intel: Optimize applications for multicore"
  • From: kimo
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: Multi-thread and memory leak
  • From: David Schwartz
• Re: experimental queued/stacked spinlock scheme...
  • From: Joe Seigh
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• experimental queued/stacked spinlock scheme...
  • From: Chris Thomasson
• Re: pthread and signals
  • From: Capstar
• Re: pthread and signals
  • From: Steve Watt
• Re: availability of lock-free approaches
  • From: Alexander Terekhov
• Re: availability of lock-free approaches
  • From: Chris Thomasson
• Re: availability of lock-free approaches
  • From: Markus Elfring
• Re: availability of lock-free approaches
  • From: David Hopwood
• Re: availability of lock-free approaches
  • From: David Hopwood
• Re: availability of lock-free approaches
  • From: Alexander Terekhov
• Re: availability of lock-free approaches
  • From: Alexander Terekhov
• Re: availability of lock-free approaches
  • From: Joe Seigh
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: availability of lock-free approaches
  • From: Chris Thomasson
• pthread and signals
  • From: Capstar
• Re: availability of lock-free approaches
  • From: David Hopwood
• Re: availability of lock-free approaches
  • From: Chris Thomasson
• Re: posix thread count
  • From: dick.dunbar
• Re: availability of lock-free approaches
  • From: Markus Elfring
• Re: Suggestion required for converting to multithreading based design
  • From: Dervish
• Re: posix thread count
  • From: Pasi Savanainen
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: GC in implementations of Java (was: availability of lock-free approaches)
  • From: Chris Thomasson
• Re: Suggestion required for converting to multithreading based design
  • From: Scott McPhillips [MVP]
• Suggestion required for converting to multithreading based design
  • From: qazmlp1209
• Re: GC in implementations of Java
  • From: Joe Seigh
• Re: Implementing Thread for Win32 Konsole-Application
  • From: joachim.zettler@xxxxxxxxxxxxxx
• Re: GC in implementations of Java (was: availability of lock-free approaches)
  • From: Chris Thomasson
• Re: Problem in detecting active thread in redhat 9
  • From: David Schwartz
• Re: availability of lock-free approaches
  • From: Joe Seigh
• Re: GC in implementations of Java (was: availability of lock-free approaches)
  • From: Chris Thomasson
• Re: GC in implementations of Java (was: availability of lock-free approaches)
  • From: Chris Thomasson
• Re: availability of lock-free approaches
  • From: Markus Elfring
• Re: GC in implementations of Java
  • From: Markus Elfring
• GC in implementations of Java (was: availability of lock-free approaches)
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Richard
• Re: availability of lock-free approaches
  • From: Joe Seigh
• Re: availability of lock-free approaches
  • From: Markus Elfring
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: Windows/cygwin pthread support
  • From: Eric Sosman
• Windows/cygwin pthread support
  • From: Mark
• Re: posix thread count
  • From: Dave Butenhof
• Re: Problem in detecting active thread in redhat 9
  • From: Marcin 'Qrczak' Kowalczyk
• Re: posix thread count
  • From: Maxim Yegorushkin
• posix thread count
  • From: Pasi Savanainen
• Problem in detecting active thread in redhat 9
  • From: uday . sen
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: David Schwartz
• Re: pthread_cancel returns 0, yet the thread is not cancelled
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• pthread_cancel returns 0, yet the thread is not cancelled
  • From: nsmith22
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: David Schwartz
• Re: beginners question - sleep in joined threads
  • From: Richard
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Maxim Yegorushkin
• Re: Implementing Thread for Win32 Konsole-Application
  • From: David Schwartz
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Chris Thomasson
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: newbie question: how to make a malloc substitute threadsafe
  • From: David Hopwood
• Re: beginners question - sleep in joined threads
  • From: Steve Watt
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Maxim Yegorushkin
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Maxim Yegorushkin
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Andy
• Re: newbie question: how to make a malloc substitue threadsafe
  • From: Maxim Yegorushkin
• Re: Thread program makes Windows XP run slow,
  • From: Dervish
• Re: WinScard.dll, ScardTransmit
  • From: joseatorralba
• newbie question: how to make a malloc substitue threadsafe
  • From: Andy
• Re: beginners question - sleep in joined threads
  • From: William MacBain
• Re: beginners question - sleep in joined threads
  • From: William MacBain
• Re: beginners question - sleep in joined threads
  • From: Sam
• Re: beginners question - sleep in joined threads
  • From: Sam
• Re: beginners question - sleep in joined threads
  • From: Joe Seigh
• Re: Implementing Thread for Win32 Konsole-Application
  • From: joachim.zettler@xxxxxxxxxxxxxx
• Re: Processor/Core count
  • From: SiBBi
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: beginners question - sleep in joined threads
  • From: Mark
• beginners question - sleep in joined threads
  • From: Sam
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Barry Kelly
• Re: Memory barriers on Windows
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Processor/Core count
  • From: Henrik Vallgren
• Re: Implementing Thread for Win32 Konsole-Application
  • From: Jim Langston
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: Processor/Core count
  • From: Eric Sosman
• Re: Processor/Core count
  • From: Henrik Vallgren
• Re: Processor/Core count
  • From: Henrik Vallgren
• Re: Processor/Core count
  • From: Henrik Vallgren
• Re: Processor/Core count
  • From: Eric Sosman
• Re: Processor/Core count
  • From: David Schwartz
• Re: Processor/Core count
  • From: Chris Friesen
• Re: Processor/Core count
  • From: Eric Sosman
• Processor/Core count
  • From: Henrik Vallgren
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Memory barriers on Windows (was: How to properly initialize shared memory)
  • From: Andrew Schetinin
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Eric Sosman
• Re: Wait Free solutions - take too much memory?
  • From: Martin James
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Dave Butenhof
• Re: pthread doubts
  • From: Dave Butenhof
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Dave Butenhof
• Re: Implementing Thread for Win32 Konsole-Application
  • From: Scott McPhillips [MVP]
• Re: Transactional Memory for Non-busy Waiting and NonTransactional actions
  • From: kimo
• Re: RCU+SMR w/ reference counting
  • From: Joe Seigh
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Joe Seigh
• Re: Implementing Thread for Win32 Konsole-Application
  • From: joachim.zettler@xxxxxxxxxxxxxx
• Re: Transactional Memory for Non-busy Waiting and NonTransactional actions
  • From: Joe Seigh
• Re: Implementing Thread for Win32 Konsole-Application
  • From: Jim Langston
• Implementing Thread for Win32 Konsole-Application
  • From: joachim.zettler@xxxxxxxxxxxxxx
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: Wait Free solutions - take too much memory?
  • From: David Schwartz
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Memory barriers on Windows (was: How to properly initialize shared memory)
  • From: Andrew Schetinin
• Re: Transactional Memory for Non-busy Waiting and NonTransactional actions
  • From: Chris Thomasson
• Re: Wait Free solutions - take too much memory?
  • From: Martin James
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: Multicore vs. multiprocessor for thread debugging
  • From: David Schwartz
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Wait Free solutions - take too much memory?
  • From: David Schwartz
• Re: Memory barriers on Windows (was: How to properly initialize shared memory)
  • From: Chris Thomasson
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: very strange pthread problem (solved)
  • From: Mark
• Memory barriers on Windows (was: How to properly initialize shared memory)
  • From: David Hopwood
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Joe Seigh
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Daniel James
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: Wait Free solutions - take too much memory?
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Multicore vs. multiprocessor for thread debugging
  • From: David Schwartz
• Re: Multicore vs. multiprocessor for thread debugging
  • From: David Schwartz
• Re: Wait Free solutions - take too much memory?
  • From: David Schwartz
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: Unbounded Page-Based Transactional Memory paper
  • From: Chris Thomasson
• Re: Transactional Memory for Non-busy Waiting and NonTransactional actions
  • From: Chris Thomasson
• Re: Unbounded Page-Based Transactional Memory paper
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Joe Seigh
• Re: Wait Free solutions - take too much memory?
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Barry Kelly
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Joe Seigh
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Joe Seigh
• Re: Wait Free solutions - take too much memory?
  • From: Joe Seigh
• Transactional Memory for Non-busy Waiting and NonTransactional actions
  • From: kimo
• Unbounded Page-Based Transactional Memory paper
  • From: kimo
• Wait Free solutions - take too much memory?
  • From: kimo
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Barry Kelly
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Barry Kelly
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: kimo
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Frank Cusack
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: kimo
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Sean Kelly
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Steve Watt
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Chris Thomasson
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Joe Seigh
• Re: newbie needs help
  • From: Richard
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: Dave Butenhof
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: John Hickin
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Chris Friesen
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Eric Sosman
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Hopwood
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Daniel James
• Re: "The Problem with Threads" - IEEE's Computer magazine article
  • From: David Schwartz
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Steve Watt
• Re: very strange pthread problem
  • From: Mark
• Re: very strange pthread problem
  • From: Jim Langston
• Re: newbie needs help
  • From: Jim Langston
• very strange pthread problem
  • From: Mark
• "The Problem with Threads" - IEEE's Computer magazine article
  • From: kimo
• newbie needs help
  • From: jdcrief
• newbie needs help
  • From: jdcrief
• Re: Question regarding multiple threads created by clone() in Linux
  • From: David Schwartz
• Re: Multicore vs. multiprocessor for thread debugging
  • From: David Schwartz
• Re: How to properly initialize shared memory on Unix?
  • From: Alexander Terekhov
• Re: Multicore vs. multiprocessor for thread debugging
  • From: Chris Friesen
• Multicore vs. multiprocessor for thread debugging
  • From: David Librik
• Re: Multi-threaded RPC on Linux (HELP!)
  • From: Eric Sosman
• Re: How to properly initialize shared memory on Unix?
  • From: David Hopwood
• Re: Multi-threaded RPC on Linux (HELP!)
  • From: nsmith22
• Re: Multi-threaded RPC on Linux (HELP!)
  • From: Eric Sosman
• Multi-threaded RPC on Linux (HELP!)
  • From: nsmith22
• Re: pthread doubts
  • From: Eric Sosman
• pthread doubts
  • From: sarathy
• Question regarding multiple threads created by clone() in Linux
  • From: vb . here
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Joe Seigh
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: How to properly initialize shared memory on Unix?
  • From: David Hopwood
• Anti-crack and anti-piracy application protection and licensing solution using code morphing.
  • From: hanzprof
• Re: Thread program makes Windows XP run slow,
  • From: Scott McPhillips [MVP]
• Thread program makes Windows XP run slow,
  • From: arun
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Pawan . Ghildiyal
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: How to properly initialize shared memory on Unix?
  • From: Chris Thomasson
• Re: How to properly initialize shared memory on Unix?
  • From: David Hopwood
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: can one mutex have multiple conditional variables?
  • From: David Schwartz
• Re: How do I view threads in UNIX on command line
  • From: Joe Seigh
• Re: How to properly initialize shared memory on Unix?
  • From: David Hopwood
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• How do I view threads in UNIX on command line
  • From: rajendra . stalekar
• Re: can one mutex have multiple conditional variables?
  • From: Valentin Nechayev
• can one mutex have multiple conditional variables?
  • From: Mark
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: How to properly initialize shared memory on Unix?
  • From: David Hopwood
• Re: How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: How to properly initialize shared memory on Unix?
  • From: Arnold Hendriks
• Re: How to properly initialize shared memory on Unix?
  • From: Jim Langston
• Re: How to properly initialize shared memory on Unix?
  • From: Jim Langston
• How to properly initialize shared memory on Unix?
  • From: Andrew Schetinin
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: rfistman@xxxxxxxxx
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: llothar
• Re: thread problem
  • From: Paul Pluzhnikov
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: Paul Pluzhnikov
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Chris Thomasson
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Joe Seigh
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: David Schwartz
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Joe Seigh
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: llothar
• thread problem
  • From: oubidoubi
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: llothar
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: David Schwartz
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: Paul Pluzhnikov
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: llothar
• Re: 1 client and multiple server
  • From: David Schwartz
• Re: Race condition while removing semaphore(sysvsem semaphore)
  • From: Joe Seigh
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: rfistman@xxxxxxxxx
• Re: Recursive mutex that can be waited upon (pthread)
  • From: David Schwartz
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: Zeljko Vrba
• Race condition while removing semaphore(sysvsem semaphore)
  • From: Pawan . Ghildiyal
• Re: Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: Paul Pluzhnikov
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Re: 1 client and multiple server
  • From: abhi147
• Transparent Fiber/ Green Thread / Coroutine Library ?
  • From: llothar
• Re: Recursive mutex that can be waited upon (pthread)
  • From: josephoswald@xxxxxxxxx
• Re: Network application design
  • From: David Schwartz
• Re: Recursive mutex that can be waited upon (pthread)
  • From: David Schwartz
• Re: Recursive mutex that can be waited upon (pthread)
  • From: josephoswald@xxxxxxxxx
• Re: Network application design
  • From: Richard
• Re: Network application design
  • From: Eric Sosman
• Network application design
  • From: sagenaut@xxxxxxxxx
• Re: 1 client and multiple server
  • From: Phil Frisbie, Jr.
• Re: want to find example code with persistent detached threads
  • From: Joe Seigh
• Re: Getting started with threads
  • From: Bo Sanden
• Re: want to find example code with persistent detached threads
  • From: Joe Seigh
• 1 client and multiple server
  • From: abhi147
• Re: Multithreaded server threads synchronization
  • From: Patrick TJ McPhee
• want to find example code with persistent detached threads
  • From: Mark
• Re: Load balancing using SCHED_RR
  • From: Steve Watt
• WinScard.dll, ScardTransmit
  • From: Ramazzotti...
• Load balancing using SCHED_RR
  • From: abhi147
• Re: Memory fence instructions on x86
  • From: David Hopwood
• Re: pthread_create, arg and local variable
  • From: grobteam
• Re: pthread_create, arg and local variable
  • From: Marcin 'Qrczak' Kowalczyk
• pthread_create, arg and local variable
  • From: grobteam
• Re: Getting started with threads
  • From: Alan Woodland
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Re: Memory fence instructions on x86
  • From: Chris
• Re: communication between threads
  • From: Steve Watt
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Herb Sutter
• Re: regarding child thread debugging
  • From: Alan Woodland
• Re: Memory fence instructions on x86
  • From: Herb Sutter
• Re: regarding child thread debugging
  • From: Dave Butenhof
• regarding child thread debugging
  • From: sunil
• communication between threads
  • From: neo
• Getting started with threads
  • From: Caroline Middlebrook
• Re: RCU+SMR w/ reference counting
  • From: Joe Seigh
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: RCU+SMR w/ reference counting
  • From: Chris Thomasson
• Re: Threadsafe singletons
  • From: Chris Thomasson
• Re: Multithreaded server threads synchronization
  • From: Lars Rune Nøstdal
• Multithreaded server threads synchronization
  • From: Pawka
• Re: RCU+SMR w/ reference counting
  • From: Joe Seigh
• Re: PLEASE HELP - C language implementation of producer-consumer model
  • From: Frank Cusack
• PLEASE HELP - C language implementation of producer-consumer model
  • From: cpptutor2000
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• RCU+SMR w/ reference counting
  • From: Joe Seigh
• Re: Memory fence instructions on x86
  • From: chris noonan
• Re: Best tools for multithreaded debugging
  • From: speedplane
• Re: how does sleep waiting on an event and triggering that event work in linux
  • From: Lars Rune Nøstdal
• Re: Sendind data to a thread
  • From: Lars Rune Nøstdal
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Dave Butenhof
• Re: Recursive mutex that can be waited upon (pthread)
  • From: TGOS
• Re: Sendind data to a thread
  • From: Sergey P. Derevyago
• Re: Sendind data to a thread
  • From: Sergey P. Derevyago
• Re: Recursive mutex that can be waited upon (pthread)
  • From: TGOS
• Re: Sendind data to a thread
  • From: David Hopwood
• Re: Linux Signal Handling SIGXCPU
  • From: llothar
• Re: Linux Signal Handling SIGXCPU
  • From: Joe Seigh
• Re: Linux Signal Handling SIGXCPU
  • From: llothar
• Linux Signal Handling SIGXCPU
  • From: llothar
• Re: Sendind data to a thread
  • From: Leslie Sanford
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Dave Butenhof
• Re: Pthreads: how to insure mutex is unlocked when a thread dies.
  • From: David Hopwood
• Re: Another term instead of GC
  • From: Steve Watt
• Re: Pthreads: how to insure mutex is unlocked when a thread dies.
  • From: Steve Watt
• Re: Pthreads: how to insure mutex is unlocked when a thread dies.
  • From: Chris Friesen
• Re: Pthreads: how to insure mutex is unlocked when a thread dies.
  • From: Sean Kelly
• Pthreads: how to insure mutex is unlocked when a thread dies.
  • From: Alan McKenney
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Recursive mutex that can be waited upon (pthread)
  • From: TGOS
• Re: Sendind data to a thread
  • From: Sean Kelly
• Re: Canceling one Thread From Another
  • From: Sean Kelly
• Re: Recursive mutex that can be waited upon (pthread)
  • From: David Hopwood
• Re: Recursive mutex that can be waited upon (pthread)
  • From: David Hopwood
• Re: Recursive mutex that can be waited upon (pthread)
  • From: David Hopwood
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Another term instead of GC
  • From: Chris
• Re: Recursive mutex that can be waited upon (pthread)
  • From: TGOS
• Re: Canceling one Thread From Another
  • From: Patrick TJ McPhee
• Re: Memory fence instructions on x86 [correction]
  • From: David Hopwood
• Re: Cannot get callstack on all threads from core file
  • From: Paul Pluzhnikov
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• how does sleep waiting on an event and triggering that event work in linux
  • From: hari . rulz
• Re: Recursive mutex that can be waited upon (pthread)
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Memory fence instructions on x86
  • From: David Hopwood
• Re: Implementing valois/michael scott lock-free reference counting
  • From: PillMonsta
• Re: Dynamic hazard pointers with Windows thread pool integration
  • From: PillMonsta
• Re: Implementing valois/michael scott lock-free reference counting
  • From: Chris Thomasson
• Re: Implementing valois/michael scott lock-free reference counting
  • From: Chris Thomasson
• Re: Dynamic hazard pointers with Windows thread pool integration
  • From: Chris Thomasson
• Re: Passing struct as an argument to a thread pool worker
  • From: Anton
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Re: Passing struct as an argument to a thread pool worker
  • From: Anton
• Re: Canceling one Thread From Another
  • From: Sean
• Re: Canceling one Thread From Another
  • From: Sean
• Re: Canceling one Thread From Another
  • From: Dave Butenhof
• Cannot get callstack on all threads from core file
  • From: ochedru
• Re: Passing struct as an argument to a thread pool worker
  • From: Martin James
• Re: Canceling one Thread From Another
  • From: Ian Collins
• Dynamic hazard pointers with Windows thread pool integration
  • From: PillMonsta
• Canceling one Thread From Another
  • From: sloughran
• Re: Passing struct as an argument to a thread pool worker
  • From: Arnold Hendriks
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: Passing struct as an argument to a thread pool worker
  • From: David Tiktin
• Re: Passing struct as an argument to a thread pool worker
  • From: Anton
• Re: Passing struct as an argument to a thread pool worker
  • From: akhodakivskiy
• Re: changing thread affinity dynamically
  • From: upadhyay . nikhil
• Re: Implementing valois/michael scott lock-free reference counting
  • From: PillMonsta
• Re: Passing struct as an argument to a thread pool worker
  • From: Martin James
• Re: pthread_cond_timedwait problem
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Memory fence instructions on x86
  • From: David Hopwood
• Re: Memory fence instructions on x86
  • From: David Hopwood
• pthread_cond_timedwait problem
  • From: Eoindeb
• Re: Implementing valois/michael scott lock-free reference counting
  • From: Joe Seigh
• Re: Implementing valois/michael scott lock-free reference counting
  • From: PillMonsta
• Re: Implementing valois/michael scott lock-free reference counting
  • From: Marcel Müller
• Re: Sendind data to a thread
  • From: Chris Thomasson
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Implementing valois/michael scott lock-free reference counting
  • From: PillMonsta
• Re: Memory fence instructions on x86
  • From: PillMonsta
• Passing struct as an argument to a thread pool worker
  • From: akhodakivskiy
• Re: Memory fence instructions on x86
  • From: chris noonan
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: Memory fence instructions on x86
  • From: David Hopwood
• Re: Memory fence instructions on x86
  • From: David Hopwood
• Re: Memory fence instructions on x86
  • From: Alexander Terekhov
• Re: Is iconv supposed to be threadsafe?
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Sendind data to a thread
  • From: Igmar Palsenberg
• Re: Sendind data to a thread
  • From: Sergey P. Derevyago
• Re: Memory fence instructions on x86
  • From: Clifford Heath
• Re: Is iconv supposed to be threadsafe?
  • From: ochedru
• Sendind data to a thread
  • From: Alex Vinokur
• Re: Best tools for multithreaded debugging
  • From: Ian Collins
• Re: The Art of Thread Synchronization?
  • From: Chris Thomasson
• Re: The Art of Thread Synchronization?
  • From: Chris Thomasson
• Re: pthread condition variable shared between processes
  • From: Steve Watt
• Re: The Art of Thread Synchronization?
  • From: Chris Thomasson
• Re: The Art of Thread Synchronization?
  • From: Chris Thomasson
• Re: Memory fence instructions on x86
  • From: Chris Thomasson
• Memory fence instructions on x86
  • From: PillMonsta
• Re: How to block a signal in all threads?
  • From: Dave Butenhof
• Re: Is iconv supposed to be threadsafe?
  • From: Marcin 'Qrczak' Kowalczyk
• Re: Best tools for multithreaded debugging
  • From: Jedrzej Dudkiewicz
• Is iconv supposed to be threadsafe?
  • From: ochedru
• Re: rmb? - was Re: Lock-free binary trees
  • From: Alexander Terekhov
• Re: The Art of Thread Synchronization?
  • From: Joe Seigh
• The Art of Thread Synchronization?
  • From: kimo
• Re: rmb? - was Re: Lock-free binary trees
  • From: Chris Thomasson
• changing thread affinity dynamically
  • From: Garima
• Re: rmb? - was Re: Lock-free binary trees
  • From: Joe Seigh
• Re: Another term instead of GC
  • From: Joe Seigh
• Re: pthread condition variable shared between processes
  • From: Casper H . S . Dik
• Re: rmb? - was Re: Lock-free binary trees
  • From: Alexander Terekhov
• Re: Best tools for multithreaded debugging
  • From: speedplane
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: rmb? - was Re: Lock-free binary trees
  • From: Joe Seigh
• Re: pthread condition variable shared between processes
  • From: Casper H . S . Dik
• Re: rmb? - was Re: Lock-free binary trees
  • From: Chris Thomasson
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: pthread condition variable shared between processes
  • From: Arnold Hendriks
• Re: pthread condition variable shared between processes
  • From: Steve Watt
• Re: pthread condition variable shared between processes
  • From: Daniel Kay
• Re: LD_ASSUME_KERNEL
  • From: Paul Pluzhnikov
• Re: PThread problem in AIX 4.3.3
  • From: rajee120
• Re: LD_ASSUME_KERNEL
  • From: lhommedumatch
• LD_ASSUME_KERNEL
  • From: lhommedumatch
• How to block a signal in all threads?
  • From: skillzero@xxxxxxxxx
• Re: pthread_cond_wait() on OpenBSD (MIPS)
  • From: ant again
• Re: pthread_cond_wait() on OpenBSD (MIPS)
  • From: Gabriel Kihlman
• pthread_cond_wait() on OpenBSD (MIPS)
  • From: ant again
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: rmb? - was Re: Lock-free binary trees
  • From: Chris Thomasson
• Re: rmb? - was Re: Lock-free binary trees
  • From: Chris Thomasson
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: David Hopwood
• Re: select() says input available, read() *sometimes* blocks
  • From: Alexis Huxley
• Re: select() says input available, read() *sometimes* blocks
  • From: David Hopwood
• Re: rmb? - was Re: Lock-free binary trees
  • From: Joe Seigh
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: Thomas Maier-Komor
• Re: select() says input available, read() *sometimes* blocks
  • From: Marcin 'Qrczak' Kowalczyk
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: davids
• Re: select() says input available, read() *sometimes* blocks
  • From: davids

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

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