From 0aa5f873fdfb391a455bc134256b7c464ffa161b Mon Sep 17 00:00:00 2001
From: Rickard Green
Date: Fri, 15 Apr 2016 11:24:14 +0200
Subject: Remove conditional dirty schedulers API
---
erts/doc/src/erl_nif.xml | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
(limited to 'erts/doc/src')
diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml
index 7546f7ef81..ef64ac66dc 100644
--- a/erts/doc/src/erl_nif.xml
+++ b/erts/doc/src/erl_nif.xml
@@ -354,10 +354,9 @@ ok
passing to it a pointer to the dirty NIF to be executed and indicating with the flags
argument whether it expects the operation to be CPU-bound or I/O-bound.
Dirty NIF support is available only when the emulator is configured with dirty
- schedulers enabled. This feature is currently disabled by default. To determine whether
- the dirty NIF API is available, native code can check to see if the C preprocessor macro
- ERL_NIF_DIRTY_SCHEDULER_SUPPORT is defined. Also, if the Erlang runtime was built
- without threading support, dirty schedulers are disabled. To check at runtime for the presence
+ schedulers enabled. This feature is currently disabled by default. The Erlang runtime
+ without SMP support currently do not support dirty schedulers even when the dirty
+ scheduler support has been enabled. To check at runtime for the presence
of dirty scheduler threads, code can use the
enif_system_info() API function.
@@ -998,10 +997,6 @@ typedef enum {
from within a dirty NIF returns true. It returns false when the calling NIF is a regular
NIF running on a normal scheduler thread, or when the emulator is built without threading
support.
- This function is available only when the emulator is configured with dirty
- schedulers enabled. This feature is currently disabled by default. To determine whether
- the dirty NIF API is available, native code can check to see if the C preprocessor macro
- ERL_NIF_DIRTY_SCHEDULER_SUPPORT is defined.
intenif_is_pid(ErlNifEnv* env, ERL_NIF_TERM term)
--
cgit v1.2.3