// Add RDMA read channel info
        writeInt4(dst, dstIndex + written, rdmaChannelInfo.getRemoteKey());
        written += 4;
        writeInt8(dst, dstIndex + written, rdmaChannelInfo.getAddress());
        written += 8;
        writeInt4(dst, dstIndex + written, rdmaChannelInfo.getLength());
        written += 4;
    }
    
    return written;
}

public static class RdmaChannelInfo {

    ]

    async def write(
        self,
        data: Annotated[
            bytes,
            Doc(
                """
                The bytes to write to the file.
                """
            ),
        ],
    ) -> None:
        """
        Write some bytes to the file.

        You normally wouldn't use this from a file you read in a request.

    name: Scorecards analysis
    runs-on: ubuntu-latest
    permissions:
      # Needed to upload the results to code-scanning dashboard.
      security-events: write
      # Needed to publish results and get a badge (see publish_results below).
      id-token: write

    steps:
      - name: "Checkout code"
        uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
        with:

        try {
            // In real implementation, this would perform RDMA write:
            // Similar to rdmaRead but with IBV_WR_RDMA_WRITE opcode

            log.debug("DiSNI RDMA write completed, {} bytes", length);

        } catch (Exception e) {
            state = RdmaConnectionState.ERROR;
            throw new IOException("DiSNI RDMA write failed", e);
        }
    }

    @Override

Directory for ReplaceSchema task

replace-schema-*.sql:
DDL statements for creation of your schema.
You should write your own DDL statements in this file.
(A SQL separator is semicolon ";")

take-finally-*.sql:
SQL statements for check loaded data (or DDL after data loading)
You should write your own SQL statements in this file.
(basically same specifications as replace-schema.sql)

The "data" directory is for data loading like this:

    /**
     * Test for the writeSetupWireFormat method.
     * It should always return 0.
     */
    @Test
    void testWriteSetupWireFormat() {
        byte[] dst = new byte[10];
        // The method should not write anything and return 0
        assertEquals(0, response.writeSetupWireFormat(dst, 0), "writeSetupWireFormat should return 0.");
    }

    /**
     * Test for the writeParametersWireFormat method.

on 16 drive MinIO deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB
file will take 200 MiB space. But, if you use ten data and six parity drives, same 100 MiB file takes around 160 MiB. If you use 14 data and
two parity drives, 100 MiB file takes only approximately 114 MiB.

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with Reader and Writers for the Xpp3 XML parser, <<<ToAPiV3()>>> and <<<ToApiV4()>>> transformers, and <<<v4>>> package
     for Merger and v4 Reader and Writers for the Xpp3 XML parser,

   * A {{{../../api/maven-api-settings/settings.html}Descriptor Reference}}

            // Write permissions
            int writeOnly = ACE.FILE_WRITE_DATA | ACE.FILE_APPEND_DATA | ACE.FILE_WRITE_ATTRIBUTES | ACE.FILE_WRITE_EA;
            assertTrue((writeOnly & ACE.FILE_WRITE_DATA) != 0, "Write should include FILE_WRITE_DATA");
            assertTrue((writeOnly & ACE.FILE_APPEND_DATA) != 0, "Write should include FILE_APPEND_DATA");

    @Throws(IOException::class)
    override fun writeTo(sink: BufferedSink) {
      val forwardingSink =
        object : ForwardingSink(sink) {
          private var totalBytesWritten: Long = 0
          private var completed = false

          override fun write(
            source: Buffer,
            byteCount: Long,
          ) {
            super.write(source, byteCount)
            totalBytesWritten += byteCount