我是新手，multitasking并且IPC我正在尝试构建一种使用共享内存进行快速进程间通信的方法（起初我正在研究 IPC 术语，考虑wcf sockets并named pipes最终发现了 MMF）。
Lock既然我已经通过 using和signalling在两个进程之间使用共享内存成功地实现了一个小型测试EventWaitHandle，那么我将采用一种实现非阻塞/无等待模式的方法。现在，我正在Thread.MemoryBarrier()尝试signalling Sector从MemoryMapedFile.
问题不明！第一轮通过，第二轮最后一次位于百慕大三角......超出了调试器的范围......
假设进程 ashowMsg()正在向进程 b发送一系列请求。
//offset positions in mmf
MemoryMappedViewAccessor MmfAcc; const int opReady= 0, opCompleteRead = 4, .....
ReadTrd()
{
//[0,3] - Reader is stationed
//[4,7] - Read Complete successfully
//[8,11] - Data-size
//[12,15] - Reader-exiting
"format" the signals Section (write zeroes).
for(;;){if (WrTrd-StepMMF1 Confimed) break;}
MmfAcc- read DataSize val @offset[8]
MmfAcc- read Data val @offset[50]
MmfAcc Write exit to offset....
....heavy use of Thread.MemoryBarrier(); sets !!! (all over the place, on every shared variable...)
}
writeTrd()
{
heavy use of Thread.MemoryBarrier() !!!
//[15-19] - wr is stationed
//[20-23] - wr Complete successfully
//[24-27] - wrExiting
"format" the signals Section .
for(;;){if Reader-StepMMF1 is Confim break;}
MmfAcc- DataSize to offset[8]
write Data To offset[50] using the method below
for(;;){if Read StepMMF2 is Confim break;}
}
当我第一次使用命名管道解决方案时，与命名管道方法相比，Mmf 方法（尽管有Lock事件等待句柄）有很大的性能提升，但我什至可以以某种方式进一步使用上述方法......？
我可以像条纹 Raid 一样克隆这种模式......
Reader1 + Reader2 & WriteThred1 + WriteThread2
所以我尝试了它并卡在了那个点上。
这是使用全内存围栏和共享内存进行信号传输的有效方法吗？
如果是这样，剩下的就是看看为什么第二次迭代失败了，性能差异。
编辑- 添加了额外线程测试背后的逻辑
这是我用来操作编写器线程的“桥梁”（读者使用相同的方法。
public void Write(byte[] parCurData)
{
if (ReadPosition < 0 || WritePosition < 0)
throw new ArgumentException();
this.statusSet.Add("ReadWrite:-> " + ReadPosition + "-" + WritePosition);
// var s = (FsMomitorIPCCrier)data;
////////lock (this.dataToSend)
////////{
Thread.MemoryBarrier();
LiveDataCount_CurIndex = dataQue.Where(i => i != null).Count();
this.dataQue[LiveDataCount_CurIndex] = parCurData;
Console.WriteLine("^^^^^" + Thread.CurrentThread.Name + " has Entered WritingThreads BRIDGE");
Console.WriteLine("^^^^^[transactionsQue] = {1}{0}^^^^^[dataQue.LiveDataASIndex = {2}{0}^^^^^[Current Requests Count = {3}{0}", "\r\n", Wtransactions, LiveDataCount_CurIndex, ++dataDelReqCount);
//this.itsTimeForWTrd2 = false;
if (Wtransactions != 0 && Wtransactions > ThrededSafeQ_Initial_Capcity - 1)
if (this.dataQueISFluded) this.DataQXpand();
if (itsTimeForWTrd2)
{
bool firstWt = true;
while (writerThread2Running)
{
if (!firstWt) continue;
Console.WriteLine("SECOND WRITERThread [2] is In The CoffeeCorner");
firstWt=false;
}
this.dataDelivery2 = this.dataQue[LiveDataCount_CurIndex];
Console.WriteLine("Activating SECOND WRITERThread [2]");
itsTimeForWTrd2 = false;
writerThread2Running = true;
//writerThread1Running = true;
writerThread2 = new System.Threading.Thread(WriterThread2);
writerThread2.IsBackground = true;
writerThread2.Name = this.DepoThreadName + "=[WRITER2]";
writerThread2.Start();
}
else
{
bool firstWt = true;
while (writerThread1Running)
{
if (!firstWt)continue;
Console.WriteLine("WRITERThread [1] is In The CoffeeCorner");
firstWt=false;
}
Console.WriteLine("Activating WRITERThread [1]");
this.dataDelivery1 = this.dataQue[LiveDataCount_CurIndex];
writerThread1Running = true;
writerThread1 = new System.Threading.Thread(WriterThread1);
writerThread1.IsBackground = true;
writerThread1.Name = this.DepoThreadName+"=[WRITER1]";
writerThread1.Start();
itsTimeForWTrd2 = true;
}
Thread.MemoryBarrier();
}
使用写句柄读写实际数据（类似的写代码）
public unsafe byte[] UsReadBytes(int offset, int num)
{
byte[] arr = new byte[num];
byte* ptr = (byte*)0;
this.accessor.SafeMemoryMappedViewHandle.AcquirePointer(ref ptr);
Marshal.Copy(IntPtr.Add(new IntPtr(ptr), offset), arr, 0, num);
this.accessor.SafeMemoryMappedViewHandle.ReleasePointer();
return arr;
}
正如我所说，我已经通过非阻塞/无等待等研究了数据和共享内存的同步问题。信号量锁，所以我试图在每个数据事务进入共享的过程中消除任何类型的开销内存映射文件。我在这里想问一下，消除 Lock 和 EventWaitHandle 并用内存栅栏的逻辑和通过 mmf 发出信号的逻辑替换它可能是什么问题？