Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mlx4: Warning: BlueFlame available, but failed to mmap() BlueFlame page #13

Open
xinxinh2020 opened this issue Aug 29, 2019 · 4 comments

Comments

@xinxinh2020
Copy link

Hi,
when i run ib_send_bw with freeflow,there is a warning: BlueFlame available, but failed to mmap() BlueFlame page, just like :
image
does this matters? becuase the ib_send_bw hangs after that, and can not get the result, i wander if this warning is related to the problem.
image

@rhiswell
Copy link

Check if FFL and FFR successfully share the same SHMEM IPC namespace, ie /dev/shm/*, otherwise ib_send_bw will be stuck since they use SHMEM to do some data-path operations when ffrouter working in fast-path mode.

Note that -e --ipc=container:router1 makes --ipc=container:router1 an environment variable instead of reusing router1's IPC namespace, so you'd better remove -e to fix it.

PS This has nothing to do with the warning you mentioned.

@xinxinh2020
Copy link
Author

Thanks very much for your helpful advice.
I follow your suggest to remove -e and it works!
Now, I have another question : How can i use low-cpu mode instead of fast-path mode?

@rhiswell
Copy link

rhiswell commented Sep 1, 2019

Just export environment variable DISABLE_FASTPATH=1 in FFL. More details can refer to here https://github.com/microsoft/Freeflow/blob/master/libraries/libibverbs-1.2.1mlnx1/src/cmd.c#L656

@xinxinh2020
Copy link
Author

i got it . Thanks for you patient reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants