Skip to content

Commit efb185f

Browse files
committed
CoreCLR: use Interlocked.MemoryBarrier() instead of Thread.MemoryBarrier()
1 parent 13e2d66 commit efb185f

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

FoundationDB.Client/Native/FdbFuture.cs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ internal bool HasAnyFlags(int flags)
154154
protected void SetFlag(int flag)
155155
{
156156
var flags = m_flags;
157-
Thread.MemoryBarrier();
157+
Interlocked.MemoryBarrier();
158158
m_flags = flags | flag;
159159
}
160160

FoundationDB.Storage.Memory/API/MemoryDatabaseHandler.cs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -429,7 +429,7 @@ internal unsafe long CommitTransaction(MemoryTransactionHandler trans, long read
429429
prev->Parent = value;
430430

431431
// make sure no thread seees an inconsitent view of the key
432-
Thread.MemoryBarrier();
432+
Interlocked.MemoryBarrier();
433433
}
434434
else
435435
{ // add this key to the data store
@@ -445,7 +445,7 @@ internal unsafe long CommitTransaction(MemoryTransactionHandler trans, long read
445445
Interlocked.Add(ref m_estimatedSize, key->Size);
446446

447447
// make sure no thread seees an inconsitent view of the key
448-
Thread.MemoryBarrier();
448+
Interlocked.MemoryBarrier();
449449

450450
if (pendingInserts != null)
451451
{

0 commit comments

Comments
 (0)