Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Read-copy-update
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Name and overview== The name comes from the way that RCU is used to update a linked structure in place. A thread wishing to do this uses the following steps: * create a new structure, * copy the data from the old structure into the new one, and save a [[pointer (computer programming)|pointer]] to the old structure, * modify the new, copied, structure, * update the global pointer to refer to the new structure, * sleep until the operating system kernel determines that there are no readers left using the old structure, for example, in the Linux kernel, by using {{mono|synchronize_rcu()}}, * once awakened by the kernel, deallocate the old structure. So the structure is ''read'' concurrently with a thread ''copying'' in order to do an ''update'', hence the name "read-copy update". The abbreviation "RCU" was one of many contributions by the Linux community. Other names for similar techniques include ''passive serialization'' and ''MP defer'' by [[VM (Operating system)|VM/XA]] programmers and ''generations'' by [[K42]] and [https://web.archive.org/web/20140102191807/http://www.eecg.toronto.edu/~tornado/ Tornado] programmers.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)