[LU-1419] Tracking ticket for gnilnd push

• Type: New Feature
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.4.0
• Labels: lnet
• Assignee: WC Triage
• Reporter: Chris Horn

Description

Cray is preparing to submit gnilnd for upstream adoption. This ticket is for tracking that work.

Comments

[Peter Jones]

Patch landed for 2.4. I suggest that any subsequent updates are handled under separate tickets for clarity.

[James A Simmons]

Found the bug in the driver causing this. The latest patch works now.

[Isaac Huang (Inactive)]

Can you reproduce it?

[James A Simmons]

I have pushed a updated driver with Isaac suggestions. The driver appears to work pretty well. The only thing I have observed with the driver is that on server node after LNET is brought up it can't ping the MGS until after I first ping the routers. Issac have any idea what could be causing that?

[James A Simmons]

Hi Cory.

I have been regularly testing master on our Gemini test bed so I have a motivation to keep this driver working If Cray doesn't mind I have no issue with keeping this driver in sync. Please look it over. The error code you can inject have changed and I just guessed what the values are so if you attempt to regression test internally this latest patch your test will most likely fail. So we need to sync up on that. Also from your earlier patch some of the Whamcloud engineers had concerns about the certain parts of the code. I didn't want to change those parts of the code without a serious inspection from the cray engineer working on this LNET driver as well. Any changes will be welcomed for testing.

[Cory Spitz]

Doug, good question. I don't know exactly, it likely won't be an instantaneous sync. However, Cray won't make code drops to match shipping versions. We intend to keep to the 'master' model. (The version submitted here is already "ahead" of our released versions). Cray will push up changes on as a regular basis as we can manage. Surely, it would be nice to stay current with 'master'. For other contributions, I suggest that we handle those as any other: through Gerrit with community review.

[Doug Oucharek (Inactive)]

Question: What will be Cray's policy for keeping the gnilnd code synchronized between the Lustre main repository and the Cray repository? Will you be doing code drops to match shipping versions? How will changes made by non-Cray community members be handled?

[Chris Horn]

http://review.whamcloud.com/#change,3381

[James A Simmons]

Attached to ticket since JIRA managed my script.

[James A Simmons]

Here is a handy script I used for re-tabbing.After you commit your code just run it and then push it upstream.
.
#!/bin/bash -e
#

1. Rewrite the last commit to remove any trailing whitespace
2. in the new version of changed lines.
3. Then replace space-based indentation with TAB based indentation
4. based on TABS at every eight position
   #
   [[ -z $TRACE ]] || set -x
   trap "rm -f $tmpf" 0
   tmpf1=$TMP/$$.1.diff
   tmpf2=$TMP/$$.2.diff
   git show --binary >$tmpf1
   perl -p -e 's/^{(+.?)[ \t]+$/$1/; while(m/}(+\t)( {1,7}

   \t|

   {8}

   )(.*)/)

   { $_=$1."\t".$3."\n"; }

   ' <$tmpf1 >$tmpf2
   if ! cmp -s $tmpf1 $tmpf2
   then
   git apply --binary --index -R --whitespace=nowarn $tmpf1
   git apply --binary --index $tmpf2
   GIT_EDITOR=true git commit --amend
   else
   echo "No changes"
   fi