[LU-1422] Cleanup Lustre cray specific code Created: 18/May/12  Updated: 03/Mar/14  Resolved: 27/Sep/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0
Fix Version/s: Lustre 2.3.0, Lustre 2.6.0

Type: Improvement Priority: Minor
Reporter: James A Simmons Assignee: Zhenyu Xu
Resolution: Fixed Votes: 0
Labels: None
Environment:

Cray nodes running Lustre


Rank (Obsolete): 4512

 Description   

In the early days of Lustre the cray Catamount system was supported. This required special blocks of code but today CRAY system use a standard Linux system so these special blocks of code are not only might not be needed but could hind performance on the CRAY platform. Such was the case recently uncoverd while doing IR testing. This ticket will be a peer view of what is and is not needed anymore.



 Comments   
Comment by Cory Spitz [ 18/May/12 ]

Thank you, James.

These special sections are conditional on CRAY_XT3. However, some of those changes were specific to CRAY Catamount using liblustre, and others not. Each CRAY_XT3 section should be examined as James suggested, and some will stay and some might go. However, the CRAY_XT3 moniker is outdated and leads to confusion so it should change in the very least. Also, for the changes that stay, we should be clear whether they are for Cray Lustre on Linux or Catamount (EOL/deprecated). We may choose to delete Catamount specifics entirely even if they were correct/useful because it is no longer used or supported.

Comment by James A Simmons [ 18/May/12 ]

Perhaps we should just drop the XT3 moniker?

Comment by James A Simmons [ 18/May/12 ]

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

Comment by Peter Jones [ 18/May/12 ]

Bobijam

Could you please review this suggested change?

Thanks

Peter

Comment by Cory Spitz [ 21/May/12 ]

I wrote, "We may choose to delete Catamount specifics entirely even if they were correct/useful because it is no longer used or supported." After more consideration, Cray is OK with removing the Catamount support.

Comment by James A Simmons [ 05/Jun/12 ]

From looking at the code the CRAY_XT3 is specific to Catamount even for the sea star case. In that case it is most likely safe to removal all the CRAY_XT3 code.

Comment by James A Simmons [ 05/Jun/12 ]

Also Cory should we remove the ulnd for sea star?

Comment by Cory Spitz [ 11/Jun/12 ]

Cray won't be maintaining the SeaStar LNDs any longer. So, we would have no objection to removing it.

Comment by Cory Spitz [ 26/Jun/12 ]

FYI: James also has http://review.whamcloud.com/#change,3064 up for review to remove Cray Catamount support (CRAY_XT3 and the portals ulnd)

Comment by James A Simmons [ 27/Jun/12 ]

Thanks for the review. Will fix in next addition. I'm going to wait to update the patch due to the LNET rewrite going on in the master branch right now. Once LU-56 is done merging I will update the patch.

Comment by Jodi Levi (Inactive) [ 27/Sep/12 ]

Please reopen ticket if more work is needed.

Comment by Cory Spitz [ 13/Sep/13 ]

James Simmons posted http://review.whamcloud.com/#/c/7469. Cray won't be maintaining the ptllnd, so we can approve its removal. However, is there something to be said about keeping the ptllnd as a reference Portals API implementation?

Generated at Sat Feb 10 01:16:29 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.