ntb.lists.linux.dev archive mirror
 help / color / mirror / Atom feed

From: Eyal ben ner <eyalbenn@gmail.com>
To: linux-ntb <linux-ntb@googlegroups.com>
Subject: ntb_tool: asymmetric windows
Date: Mon, 15 Nov 2021 08:51:46 -0800 (PST)	[thread overview]
Message-ID: <24826bb2-da96-4ea8-9b75-6f40425e0368n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1797 bytes --]




Hi,

Newbie question: I'm using 2 Xeon(R) Silver 4214 nodes (ntb3 hw) with 
4.19.177 kernel.

I loaded the ntb_tool modules and connected both nodes.

I created 8KB buffer on node A, I mapped a (8KB) window on node B, I wrote 
8KB file to the window and succeed to read the file completely from the 
debugfs on node A (so far, we are good).

I restarted node A buffer content.

Next, I created additional 4KB buffer on node B, then I wrote the same 8KB 
file to the same old 8KB window on node B, but now I read only 4KB on node 
A, the rest 4KB is the initialized data of the buffer.

Below I'll put the exact commands I used.

Is this a knows issue?

Any idea how to solve this issue?

 

Thanks,

Eyal

 

1st stage:

Node A:

1.      insmod ntb/test/ntb_tool.ko

Node B:

1.      insmod ntb/test/ntb_tool.ko 

Node A:

1.      export DBG_DIR=/sys/kernel/debug/ntb_tool/0000:0a:00.0

2.      cat $DBG_DIR/peer0/link

3.      echo Y > $DBG_DIR/link

4.      cat $DBG_DIR/peer0/link

Node B:

1.      export DBG_DIR=/sys/kernel/debug/ntb_tool/0000:0a:00.0

2.      cat $DBG_DIR/peer0/link

3.      echo Y > $DBG_DIR/link

4.      cat $DBG_DIR/peer0/link

Node A:

1.      echo 8192 > $DBG_DIR/peer0/mw_trans0

2.      cat 2.txt > $DBG_DIR/peer0/mw

3.      head -c 8192 $DBG_DIR/peer0/mw0 > 1s_1st_r.txt

Node B:

1.      echo 0x1000000000:8192  > $DBG_DIR/peer0/peer_mw_trans0

2.      cat 5.txt  > $DBG_DIR/peer0/peer_mw0

Node A:

1.      head -c 8192 $DBG_DIR/peer0/mw0 > 1s_2nd_r.txt

 

2nd stage:

Node B:

1.      echo 4096 > $DBG_DIR/peer0/mw_trans0

Node A:

1.      cat 2.txt > $DBG_DIR/peer0/mw0

2.      head -c 8192 $DBG_DIR/peer0/mw0 > 2s_1st_r.txt

Node B:

1.      cat 5.txt  > $DBG_DIR/peer0/peer_mw0

Node A:

1.      head -c 8192 $DBG_DIR/peer0/mw0 > 2s_2nd_r.txt

 

 

 

[-- Attachment #1.2: Type: text/html, Size: 3247 bytes --]

                 reply	other threads:[~2021-11-15 16:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=24826bb2-da96-4ea8-9b75-6f40425e0368n@googlegroups.com \
    --to=eyalbenn@gmail.com \
    --cc=linux-ntb@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).