[LU-9472] FastReg (MLX5) support breaks when map_on_demand > 0 Created: 09/May/17 Updated: 08/Sep/17 Resolved: 20/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0, Upstream |
| Fix Version/s: | Lustre 2.10.0, Upstream |
| Type: | Bug | Priority: | Critical |
| Reporter: | Doug Oucharek (Inactive) | Assignee: | Doug Oucharek (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | lnet | ||
| Issue Links: |
|
||||||||||||||||||||
| Severity: | 3 | ||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||
| Description |
|
When building against MODED 4, the default for map_on_demand switches from 0 to 256. This is breaking MLX5-based cards which make use of the FastReg support in ko2iblnd. There are three problems with FastReg which need to be fixed:
The first 2 items are blockers and must be fixed ASAP. The 3rd might as well be addressed at the same time.
|
| Comments |
| Comment by Doug Oucharek (Inactive) [ 09/May/17 ] |
|
The main problem, it turns out, is that the unmap routine is never being called for FastReg. As such, we have to keep growing the pool and assert when trying to shut down networking (because pool items are leaking). |
| Comment by James A Simmons [ 09/May/17 ] |
|
Thanks for finding this. |
| Comment by Gerrit Updater [ 09/May/17 ] |
|
Doug Oucharek (doug.s.oucharek@intel.com) uploaded a new patch: https://review.whamcloud.com/27015 |
| Comment by Alexey Lyashkov [ 15/May/17 ] |
|
Tested fix and it work for me. |
| Comment by Gerrit Updater [ 20/May/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/27015/ |
| Comment by Peter Jones [ 20/May/17 ] |
|
Landed for 2.10 |
| Comment by Doug Oucharek (Inactive) [ 17/Aug/17 ] |
|
Has this been pushed upstream yet? |
| Comment by James A Simmons [ 17/Aug/17 ] |
|
Not yet. |