PR_SetConcurrency

NSPR
About NSPR
NSPR API Reference
NSPR Build Instruction
NSPR Release Process
Introduction to NSPR
NSPR Types
Threads
1. Threading Types and Constants
2. Threading Functions
Process Initialization
Locks
1. Lock Type
2. Lock Functions
Condition Variables
1. Condition Variable Type
2. Condition Variable Functions
Monitors
1. Monitor Type
2. Monitor Functions
Cached Monitors
1. Cached Monitor Functions
I/O Types
I/O Functions
Network Addresses
1. Network Address Types and Constants
2. Network Address Functions
Atomic Operations
Interval Timing
1. Interval Time Type and Constants
2. Interval Functions
Date and Time
Memory Management Operations
1. Memory Allocation Functions
2. Memory Allocation Macros
String Operations
Floating Point Number to String Conversion
Linked Lists
1. Linked List Types
  1. PRCList
2. Linked List Macros
Dynamic Library Linking
Process Management and Interprocess Communication
1. Process Management Types and Constants
  1. PRProcess
  2. PRProcessAttr
2. Process Management Functions
  1. Setting the Attributes of a New Process
  2. Creating and Managing Processes
Logging
Named Shared Memory
1. Shared Memory Protocol
2. Named Shared Memory Functions
Anonymous Shared Memory
1. Anonymous Memory Protocol
2. Anonymous Shared Memory Functions
IPC Semaphores
1. IPC Semaphore Functions
Thread Pools
1. Thread Pool Types
2. Thread Pool Functions
Random Number Generator
1. Random Number Generator Function
Hash Tables
1. Hash Tables and Type Constants
2. Hash Table Functions
NSPR Error Handling
Contribute
2. The MDN Project

Syntax

Parameter

Description

Setting concurrency controls the number of virtual processors that NSPR uses to implement its M x N threading model. The M x N model is not available on all host systems. On those where it is not available, PR_SetConcurrency is ignored.

Virtual processors are actuallyglobal threads, each of which is designed to support an arbitrary number oflocal threads. Since global threads are scheduled by the host operating system, this model is particularly applicable to multiprocessor architectures, where true parallelism is possible. However, it may also prove advantageous on uniprocessor systems to reduce the impact of having a locally scheduled thread calling incidental blocking functions. In such cases, all the threads being supported by the virtual processor will block, but those assigned to another virtual processor will be unaffected.