
Kernel OFI Repro Layout and Naming Framework
Explore the layout and naming conventions for the Kernel OFI project, including details on module naming, testing, providers, and file structure. Learn about the rational behind kfabric and rdma inclusion and the organization of header files.
Uploaded on | 0 Views
Download Presentation

Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Kernel OFI repro layout and naming Frank Yang, Chen Zhao Netapp PPG Stan Smith Intel SSG/DPD May, 2015
Kernel OFI Naming Repro naming kfabric/ API naming kfi_*() vs. fi_*() ? Use kfi_*() throughout Use fi_*() throughout Hybrid kfi_*()for providers (exports DOWN) fi_*() for clients (exports UP) 2 www.openfabrics.org
Module naming Framework: kfabric.ko Test: kfit_xxx.ko kfi_test_xxx.ko Providers: kfi_xxx.ko - kfi_verbs.ko Kfip_xxx.ko - kfip_ibv.ko 3 www.openfabrics.org
Kernel OFI Repro Layout kfabric kfi prov include Makefile man tests (framework) (providers) kfabric.c ibverbs socket ibverbs socket 4 www.openfabrics.org
Makefile(s) kfabric/Makefile would build everything for the current running kernel; with other kernel.org kernel possible. Entire build is out-of-kernel as we do not yet know where kfabric/ would land in the kernel src tree. Could be under drivers/ or net/ ? kfabric/prov/ibverbs/Makefile would build kfip_ibv.ko (IB provider). kfabric/tests/Makefile would build all tests under kfabric/tests/* ibverbs/* 5 www.openfabrics.org
Part of the rational behind kfabric/include/rdma is within kfabric/include are common .h files used by all providers. Partitioning such that provider header files are not mixed with API header files in kfabric/include/rdma. Honestly, I ve never liked the rdma/ name, include/api/ or something other than rdma/ would work? Provider builds search ../../include/ and ../../kfi/ 6 www.openfabrics.org