Content-Length: 9145 | pFad | http://lwn.net/Articles/66370/

Read-copy-update and interrupt latency [LWN.net]
|
|
Subscribe / Log in / New account

Read-copy-update and interrupt latency

Read-copy-update and interrupt latency

Posted Jan 15, 2004 10:51 UTC (Thu) by oak (guest, #2786)
Parent article: Read-copy-update and interrupt latency

What's the effect of RCU code on single CPU machines?


to post comments

Read-copy-update and interrupt latency

Posted Jan 16, 2004 23:32 UTC (Fri) by PaulMcKenney (✭ supporter ✭, #9624) [Link]

It defers deletion, similar to SMP kernels. For an example of why this is needed, consider an interrupt handler (perhaps softirq) that deletes an element from a data structure that can be referenced from mainline code. The interrupt handler then cannot immediately free up the element, since the interrupted mainline code might well still be referencing it.

There are cases where it -is- safe to immediately free things up in an UP kernel, and Dipankar has some code that permits this in some cases as well.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds









ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://lwn.net/Articles/66370/

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy