Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming.threads > #4665 > unrolled thread

Transactional Memory Everywhere: I/O Operations

Back to article view | Back to comp.programming.threads

Contents

  Transactional Memory Everywhere: I/O Operations Horizon68 <horizon@horizon.com> - 2018-10-03 12:16 -0700

#4665 — Transactional Memory Everywhere: I/O Operations

Hello,


Transactional Memory Everywhere: I/O Operations

One can execute I/O operations within a lock-based critical section, 
and, at least in principle, from within an RCU read-side critical 
section.  What happens when you attempt to execute an I/O operation from 
within a transaction?

The underlying problem is that transactions may be rolled back, for 
example, due to conflicts.  Roughly speaking, this requires that all 
operations within any given transaction be idempotent, so that executing 
the operation twice has the same effect as executing it once. 
Unfortunately, I/O is in general the prototypical non-idempotent 
operation, making it difficult to include general I/O operations in 
transactions.

Read more here:

https://mirrors.edge.kernel.org/pub/linux/kernel/people/paulmck/Answers/TransactionalMemoryEverywhere/IO.html


Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]

Back to top | Article view | comp.programming.threads

csiph-web