`_`, `<`, and `>` are special characters in Markdown, and need to be
escaped except in code blocks. So backticks or backslahes are used to
fix the apparent issues, which caused wrong rendering.
Signed-off-by: Wu Yongwei <wuyongwei@gmail.com>
Currently, the following architectures are supported:
- x86 (i386, i486, i586, i686)
Currently, the following architectures are supported:
- x86 (i386, i486, i586, i686)
- PowerPC 32/64
- S390, S390x
- ARM 32/64
- PowerPC 32/64
- S390, S390x
- ARM 32/64
-The API members start with the prefix "urcu_<flavor>_", where
-<flavor> is the chosen flavor name.
+The API members start with the prefix `urcu_<flavor>_`, where
+`<flavor>` is the chosen flavor name.
### Usage of `liburcu-memb`
### Usage of `liburcu-memb`
./configure --enable-rcu-debug
For fine grained enabling of debugging self-checks, build
./configure --enable-rcu-debug
For fine grained enabling of debugging self-checks, build
-userspace-rcu with DEBUG_RCU defined and compile dependent
-applications with DEBUG_RCU defined when necessary.
+userspace-rcu with `DEBUG_RCU` defined and compile dependent
+applications with `DEBUG_RCU` defined when necessary.
Warning: Enabling this feature result in a performance penalty.
Warning: Enabling this feature result in a performance penalty.
Userspace RCU 0.11 or 0.12 shared objects. The problem occurs as
follows:
Userspace RCU 0.11 or 0.12 shared objects. The problem occurs as
follows:
- - An application executable is built with _LGPL_SOURCE defined, includes
+ - An application executable is built with `_LGPL_SOURCE` defined, includes
any of the Userspace RCU 0.10 urcu flavor headers, and is built
without the -fpic compiler option.
any of the Userspace RCU 0.10 urcu flavor headers, and is built
without the -fpic compiler option.
-Stack with wait-free push and wait-free pop_all. Both
+Stack with wait-free push and wait-free pop\_all. Both
blocking and non-blocking pop and traversal operations are provided. This
stack does _not_ specifically rely on RCU. Various synchronization techniques
can be used to deal with pop ABA. Those are detailed in the API.
blocking and non-blocking pop and traversal operations are provided. This
stack does _not_ specifically rely on RCU. Various synchronization techniques
can be used to deal with pop ABA. Those are detailed in the API.
-Stack with lock-free push, lock-free pop, wait-free pop_all,
+Stack with lock-free push, lock-free pop, wait-free pop\_all,
wait-free traversal. Various synchronization techniques can be
used to deal with pop ABA. Those are detailed in the API.
This stack does _not_ specifically rely on RCU.
wait-free traversal. Various synchronization techniques can be
used to deal with pop ABA. Those are detailed in the API.
This stack does _not_ specifically rely on RCU.
* gsed
* gmake
* pkgconfig
* gsed
* gmake
* pkgconfig