https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-11064 Lustre <p>We're allowed to start at a non-aligned page offset in the first fragment and end at a non-aligned page offset in the last fragment.</p> <p>Currently the first fragment is not considered. So it's possible to start on a non-aligned page boundary and consider that there is a gap in the transmit buffer, which is not correct.</p> LU-11064

o2iblnd fast reg gaps case is determined incompletely

Bug Major Resolved Fixed Amir Shehata Amir Shehata Wed, 30 May 2018 20:05:26 +0000 Tue, 9 Jul 2019 17:18:38 +0000 Wed, 18 Jul 2018 12:28:56 +0000 Lustre 2.11.0 Lustre 2.12.0 1 7 <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/32586" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32586</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11064" title="o2iblnd fast reg gaps case is determined incompletely " class="issue-link" data-issue-key="LU-11064"><del>LU-11064</del></a> lnd: determine gaps correctly<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: d2105fede63b081a61fb8c77683d79d7991693f5</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/32586/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32586/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11064" title="o2iblnd fast reg gaps case is determined incompletely " class="issue-link" data-issue-key="LU-11064"><del>LU-11064</del></a> lnd: determine gaps correctly<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: e40ea6fd4494b86d26a9d459f7bf620d816af4e1</p> <p>Landed for 2.12</p> <p>Does this LU impact 2.10.x ?</p> <p>Plane 2.10.x doesn't include any of the GAPs changes. These were landed in 2.11.</p> <p>However, if you applied these patches on your own branch based on 2.10.x, then you'll need that patch as well.</p> <p>patches I'm talking about are:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> LU-9943 lnd: correct WR fast reg accounting LU-9810 lnd: use less CQ entries <span class="code-keyword">for</span> each connection LU-10129 lnd: rework map_on_demand behavior LU-10129 lnd: set device capabilities</pre> </div></div> <p>We have cherry-picked "<a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a> lnd: use less CQ entries for each connection". Not the other three.</p> <p> </p> <p>FYI, We cherry-picked <a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a> into 2.11.</p> <p>Mahmoud</p> <p>My recommendation is to open a ticket to ask whether it is ok before you include any patch into your distribution - sometimes there are non-obvious pre-requisites.</p> <p>Peter</p> <p>I think 9810 should be ok. There's just been a lot of rework in that area regarding map_on_demand and usage of gaps in 2.11. So I wouldn't recommend pulling that in to a tree based on 2.10.x, unless you pull in the entire set of changes.</p> <p>Based on <a href="https://jira.whamcloud.com/browse/LU-11308" title=" LustreError: 2742:0:(events.c:199:client_bulk_callback()) event type 2, status -90, desc ffff8807e3876400" class="issue-link" data-issue-key="LU-11308"><del>LU-11308</del></a>, I think you guys might be using trees based on 2.10.X as well as 2.11. That's why I was making sure you guys are aware of the dependencies there.</p> <p>Well, we actually have<br/> <a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a>: lnd: use less CQ entries for each connection, and<br/> <a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a> lnet: fix build with M-OFED 4.1<br/> in our 2.10.3 and 2.10.5 branches.</p> <p><a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a> was included in Whamcloud's 2.11.0 release. I cherry-picked <a href="https://jira.whamcloud.com/browse/LU-11064" title="o2iblnd fast reg gaps case is determined incompletely " class="issue-link" data-issue-key="LU-11064"><del>LU-11064</del></a> into our 2.11.0.</p> <p>Mahmoud has decided to run 2.10.x. So what do you recommend us to do? I do not recall why I cherry-picked <a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a>, do you Mahmoud? Probably trying to fix a problem we encountered?</p> <p><a href="https://jira.whamcloud.com/browse/LU-9810" title="Melanox OFED 4.1 support" class="issue-link" data-issue-key="LU-9810"><del>LU-9810</del></a> added mofed4.x support. I don't think we cherry-picked that one.</p> <p>Would it be possible to point me to the 2.10.X git repo that you guys are using now, so I can take a look at the commits. This way I'm clear on which patches you have.</p> <p>How about we transfer this discussion to a new ticket so we can identify it as a NASA support issue?</p> <p>Admir, <br/> <a href="https://github.com/jlan/lustre-nas" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/jlan/lustre-nas</a></p> <p> </p> Duplicate LU-11308 LU-11105 Related LU-11350 Development Rank 1|hzzxyn: Rank (Obsolete) 9223372036854775807 Severity