Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-10300

Can the Lustre 2.10.x clients support 64K kernel page?

Details

    • Question/Request
    • Resolution: Cannot Reproduce
    • Major
    • None
    • Lustre 2.10.0
    • None
    • Redhat
    • 9223372036854775807

    Description

      We test Lustre in the kernel 4.11.0 which use 64K memory page, and we found that there are no config items in the configure.

      Attachments

        Issue Links

          Activity

            [LU-10300] Can the Lustre 2.10.x clients support 64K kernel page?

            The aarch64 clients are working with any recent Lustre release.

            adilger Andreas Dilger added a comment - The aarch64 clients are working with any recent Lustre release.

            "James Simmons <jsimmons@infradead.org>" uploaded a new patch: https://review.whamcloud.com/45962
            Subject: LU-10300 test: does arm testing work
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 2036c3298804defa44e0457e65893e91d1da3985

            gerrit Gerrit Updater added a comment - "James Simmons <jsimmons@infradead.org>" uploaded a new patch: https://review.whamcloud.com/45962 Subject: LU-10300 test: does arm testing work Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 2036c3298804defa44e0457e65893e91d1da3985

            James, I'd suggest to move your previous comment into a separate ticket related to 64KB PAGE_SIZE on the server, and leave this one for tracking 64KB PAGE_SIZE on the client. I suspect most people care about client-side support more than server-side, and this will help understand which issues are important to fix for the two different cases. In any case, it doesn't make sense to have multiple independent issues being worked on in the same Jira ticket.

            adilger Andreas Dilger added a comment - James, I'd suggest to move your previous comment into a separate ticket related to 64KB PAGE_SIZE on the server, and leave this one for tracking 64KB PAGE_SIZE on the client. I suspect most people care about client-side support more than server-side, and this will help understand which issues are important to fix for the two different cases. In any case, it doesn't make sense to have multiple independent issues being worked on in the same Jira ticket.

            This time I tested ZFS lustre servers using the ethernet interface and it worked. Currently their is a bug in the RHEL7 alt kernel that I'm using in netlink that shows up when using k2oiblnd for some reason. Their appears to be a fix but requires rebuild the RHEL7 alt kernel. Now to test ldiskfs.

            simmonsja James A Simmons added a comment - This time I tested ZFS lustre servers using the ethernet interface and it worked. Currently their is a bug in the RHEL7 alt kernel that I'm using in netlink that shows up when using k2oiblnd for some reason. Their appears to be a fix but requires rebuild the RHEL7 alt kernel. Now to test ldiskfs.
            simmonsja James A Simmons added a comment - - edited

            So I have managed to get Lustre ZFS servers running on Power8 nodes. I got it to mount and then it just locked up with any attempt to use the file system  Well its a start

            simmonsja James A Simmons added a comment - - edited So I have managed to get Lustre ZFS servers running on Power8 nodes. I got it to mount and then it just locked up with any attempt to use the file system  Well its a start

            Once the RHEL ARM/Power8 server support work is complete we can test 64K pages on the server side.

            simmonsja James A Simmons added a comment - Once the RHEL ARM/Power8 server support work is complete we can test 64K pages on the server side.

            It probably makes sense to print a build warning in the server code when PAGE_SIZE isn't 4096, just so people are aware that this isn't being tested. If someone starts testing this in the future, the warning can be removed.

            adilger Andreas Dilger added a comment - It probably makes sense to print a build warning in the server code when PAGE_SIZE isn't 4096, just so people are aware that this isn't being tested. If someone starts testing this in the future, the warning can be removed.

            Yes, I tested the 64KB PAGE_SIZE server with 4KB PAGE_SIZE Client and 64KB PAGE_SIZE Client, there are some errors both in these two clients.Thanks for help !

            Red ZhangWei (Inactive) added a comment - Yes, I tested the 64KB PAGE_SIZE server with 4KB PAGE_SIZE Client and 64KB PAGE_SIZE Client, there are some errors both in these two clients.Thanks for help !

            We definitely used to run Lustre with 64KB PAGE_SIZE on IA64 clients, and in theory this would still work but we haven't tested it in a long time.  We never had much success with 64KB PAGE_SIZE on the server, since this caused problems with 4KB PAGE_SIZE clients doing writes to the 64KB PAGE_SIZE server.

            adilger Andreas Dilger added a comment - We definitely used to run Lustre with 64KB PAGE_SIZE on IA64 clients, and in theory this would still work but we haven't tested it in a long time.  We never had much success with 64KB PAGE_SIZE on the server, since this caused problems with 4KB PAGE_SIZE clients doing writes to the 64KB PAGE_SIZE server.

            Thanks for your replay, with the map_ondemand enabled, can the Lustre only support 4k kernel memory page?

            Red ZhangWei (Inactive) added a comment - Thanks for your replay, with the map_ondemand enabled, can the Lustre only support 4k kernel memory page?

            People

              simmonsja James A Simmons
              Red ZhangWei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: