Can the spinlock implementation on xv6 not require __sync_synchronize?
While studying spinlocks in xv6, I encountered acquire barriers and release barriers. After researching and learning about them, my understanding is as follows:
Can the spinlock implementation on xv6 not require __sync_synchronize?
While studying spinlocks in xv6, I encountered acquire barriers and release barriers. After researching and learning about them, my understanding is as follows:
Can the spinlock implementation on xv6 not require __sync_synchronize?
While studying spinlocks in xv6, I encountered acquire barriers and release barriers. After researching and learning about them, my understanding is as follows:
Can the spinlock implementation on xv6 not require __sync_synchronize?
While studying spinlocks in xv6, I encountered acquire barriers and release barriers. After researching and learning about them, my understanding is as follows:
Can the spinlock implementation on xv6 not require __sync_synchronize?
While studying spinlocks in xv6, I encountered acquire barriers and release barriers. After researching and learning about them, my understanding is as follows: