## 3. RDMA Architecture

### 3.1 RDMA Capabilities
```java
public enum RdmaCapability {
    RDMA_READ,           // Remote direct read operations
    RDMA_WRITE,          // Remote direct write operations  
    RDMA_SEND_RECEIVE,   // Traditional send/receive with RDMA
    MEMORY_REGISTRATION, // Dynamic memory registration
    FAST_REGISTRATION   // Fast memory region registration
}

    /**
     * Test doGet with NTLM authentication for directory listing
     * This test verifies the authentication flow without actual network operations
     */
    @Test
    void testDoGet_DirectoryListing() throws Exception {
        // Create a test-specific NetworkExplorer that mocks file operations
        networkExplorer = new NetworkExplorer() {
            @Override

            // Some operations might succeed before key wipe, some might fail after
            // At minimum, we expect some activity (not all operations should be no-ops)
            int totalOperations = successCount.get() + failureCount.get();
            assertTrue(totalOperations > 0, "Some signing/verification operations should have been attempted");
        }

        @Test

 * <li><code>TransactNamedPipe</code> A message-type pipe call that
 * writes to and reads from an existing pipe descriptor in one operation.
 * <li><code>CreateFile</code>, <code>ReadFile</code>,
 * <code>WriteFile</code>, and <code>CloseFile</code> A byte-type pipe can
 * be opened, written to, read from and closed using the standard Win32
 * file operations.
 * </ul>
 *
 * <p>

        CIFSException expectedException = new CIFSException("Watch operation failed");
        when(watchHandle.watch()).thenThrow(expectedException);

        // Execute and verify
        CIFSException thrown = assertThrows(CIFSException.class, () -> {
            watchHandle.watch();
        });

        assertEquals("Watch operation failed", thrown.getMessage());
        verify(watchHandle, times(1)).watch();
    }

Sebastián Ramírez <******@****.***> 1731896744 +0100

    }

    @Test
    @DisplayName("EmptyIterator should handle remove operations multiple times")
    void testMultipleRemoveOperations() {
        // When & Then
        assertDoesNotThrow(() -> {
            emptyIterator.remove();
            emptyIterator.remove();
            emptyIterator.remove();
        }, "Multiple remove operations should not cause issues");

		atomic.AddUint64(&p.operations[s], 1)
		if s < scannerMetricLastRealtime {
			p.latency[s].addSize(duration, int64(sz))
		}
	}
}

// incTime will increment time on metric s with a specific duration.
// Use for s < scannerMetricLastRealtime
func (p *scannerMetrics) incTime(s scannerMetric, d time.Duration) {
	atomic.AddUint64(&p.operations[s], 1)
	if s < scannerMetricLastRealtime {

   * changes the contents of the transposed table and vice versa.
   *
   * <p>The returned table supports update operations as long as the input table supports the
   * analogous operation with swapped rows and columns. For example, in a {@link HashBasedTable}
   * instance, {@code rowKeySet().iterator()} supports {@code remove()} but {@code

 *
 * This class implements the TRANS_TRANSACT_NAMED_PIPE transaction which
 * combines writing data to a pipe and reading the response in a single operation.
 * This is more efficient than separate write and read operations.
 */
public class TransTransactNamedPipe extends SmbComTransaction {

    private static final Logger log = LoggerFactory.getLogger(TransTransactNamedPipe.class);