Hi,

Some of the sample applications seem to assume that the reported RQ size is always greater or equal than SQ size. This is not required. The call to create QP uses the same value for RQ and SQ.
Coming from min(maxCQ, maxRQ), which may fail if SQ turned out to be reported in adapter info as smaller than maxCQ and maxRQ.

Please find below a potential fix for ndping.
Thanks.

Fix to asymetrically reported QP sizes

  This patch incorporates the Initiator queue depth reported through
  AdapterInfo.

  When reported sizes for SQ are smaller than RQ, createQP uses
  min(CQDepth,RQDepth) for both SQ and RQ causing QP creation errors.

diff --git a/src/examples/ndping/ndping.cpp b/src/examples/ndping/ndping.cpp
index 8a08a12..deac1fb 100644
--- a/src/examples/ndping/ndping.cpp
+++ b/src/examples/ndping/ndping.cpp
@@ -62,7 +62,8 @@ public:

       ND2_ADAPTER_INFO adapterInfo = { 0 };
       NdTestBase::GetAdapterInfo(&adapterInfo);
-        m_queueDepth = min(adapterInfo.MaxCompletionQueueDepth, adapterInfo.MaxReceiveQueueDepth);
+        m_queueDepth = min(adapterInfo.MaxReceiveQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(m_queueDepth, adapterInfo.MaxCompletionQueueDepth);
       m_queueDepth = (queueDepth != 0) ? min(queueDepth, m_queueDepth) : m_queueDepth;
       m_inlineSizeThreshold = adapterInfo.InlineRequestThreshold;

@@ -195,7 +196,8 @@ public:

       ND2_ADAPTER_INFO adapterInfo;
       NdTestBase::GetAdapterInfo(&adapterInfo);
-        m_queueDepth = min(adapterInfo.MaxCompletionQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(adapterInfo.MaxReceiveQueueDepth, adapterInfo.MaxInitiatorQueueDepth);
+        m_queueDepth = min(m_queueDepth, adapterInfo.MaxCompletionQueueDepth);
       m_queueDepth = (queueDepth != 0) ? min(queueDepth, m_queueDepth) : m_queueDepth;
       m_inlineSizeThreshold = adapterInfo.InlineRequestThreshold;

On one adapter, when two process call RegisterDataBuffer at same time, the Register function may not return, is it a problem?

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

HI, I am an engineer working on the RDMA IWARP protocol.

I use chelsio t6225-cr NIC Adapter and connect 2 pc back to back.

Development environment is Window10, and i use NDSPI( NDSPI Interfaces (Windows) ).

i want to register 1TB Memory to my adapter by using INDAdapter::RegisterMemory Method.

But I can't register more than 128GB of memory ,I use this function in the following way.

for (int i = 0; i < memCount; i++)
{
  hr = pAdapter->RegisterMemory(Buffers, BuffSize, pOv, &hMrs);
  if (hr == ND_PENDING)
  {
   SIZE_T BytesRet;
   hr = pAdapter->GetOverlappedResult(pOv, &BytesRet, TRUE);
  }
  if (FAILED(hr))
  {
   printf("RegisterMemory Failed with %08x\n", hr);
   exit(__LINE__);
  }
}

BuffSize = 65000 * 65000 ≒ 4GB, and memCount = 32

When i = 0~30, hr return S_OK , But i = 31 hr returns 0x0000009A (insufficient system resources exist to complete the api)

Even if the buffer size is reduced and the number of registrations is increased, the same problem occurs near 128GB

Is there a limit to registering memory above a certain number?

How can i register over 128GB?? i must regist 1TB memory to achieve My goal.

If anyone has tried something similar using the Celsio T6 adapter or another NIC, can you tell me how?

GetSystemTimes return sum of the designated times across all processors, so there is no need to multiply the result by CpuCount().

GetSystemTimes function (processthreadsapi.h)

Change proposed for GetCpuTime method of CpuMonitor class in ndcommon.h :
return (100.0 - (((endIdle - startIdle) * 100) / (endCpu - startCpu)));

VS 2022 complains with warning C5205 because Provider abstract class defines a non virtual destructor, which may lead to undefined behaviour as objects destruction in ndfrmwrk.cpp use static binding instead of dynamic binding.

Suggested correction :

• To ensure all destructors are called, nedd to change ~Provider(void); to virtual ~Provider(void); in ndprov.h
• Should also comment (or delete) ~NdV1Provider(); and ~NdProvider(); definitions, since these derived constructors are not implemented.
• Finally, suppress AdditionalOptions /Wv:18 added by PR ADD AdditionalOptions Wv:18

tried to build MS-MPI with the NetworkDirect library
version 2.0.1 on https://www.nuget.org/packages/networkdirect

@jithinjosepkl
please update the version on GITHUB in accordance with NUGET

freshly installed visual studio 2017 and windows driver kit 10

• pull code from github
• opening solution 'netdirect'
• projects ndutil and ndtestutil fail to load.
  If asking to reload the projects, a dialog box is shown saying that something went wrong in WindowsDriver.UserMode.Default.props: a numeric comparison was attempted on "$(_NT_TARGET_VERSION)" that evaluates to "" instead of a number, in condition "$(_NT_TARGET_VERSION) >= $(_NT_TARGET_VERSION_WIN10)"

Windows platform and linux platform use rdma communication, linux use rdma_verbs as server, windows use ndspi communication, server receives remoteaddress and remoteToken sent by peer post_send operation, and performs IBV_WR_RDMA_READ operation, and the error code received when poll cq is IBV_WC_REM_ACCESS_ERR, observed The client-side memory permission is set to ND_MR_FLAG_ALLOW_REMOTE_READ | ND_MR_FLAG_ALLOW_REMOTE_WRITE, and the MW is set to ND_OP_FLAG_ALLOW_READ | ND_OP_FLAG_ALLOW_WRITE.

• using freshly installed VS2022
• using 043f1bf
• trying to open the solution fails with the message above.
• there is no "GetType" anywhere in the .vcxproj files mentioned in the error output
• could this be because the solution relies on deprecated CBT ? (https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/6.0/calling-gettype-property-functions)

Tried multiple applications(like ndping, ndpingpong, ndrping etc..) to connect with ND 1.0 supported providers and is failing with below errors.

PS C:\Users\Administrator> .\ndrping.exe -c -p 102.1.1.134
Beginning test: ndrping.exe
Test Failed.
Failed open adapter.