| Horizon68 <horizon@horizon.com>: Oct 03 12:16PM -0700 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. |
| Horizon68 <horizon@horizon.com>: Oct 03 10:37AM -0700 Hello.. My C++ synchronization objects library was updated.. My Scalable RWLocks using scalable counting networks were enhanced.. I think my C++ synchronization objects library is much more stable and fast. You can read about it and download the new Windows and Linux versions from: https://sites.google.com/site/scalable68/c-synchronization-objects-library Thank you, Amine Moulay Ramdane. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com. |
No comments:
Post a Comment