Contributor’s Guidelines

• 1. DPDK Coding Style
  • 1.1. Description
  • 1.2. General Guidelines
  • 1.3. C Comment Style
  • 1.4. C Preprocessor Directives
  • 1.5. C Types
  • 1.6. Naming
  • 1.7. C Indentation
  • 1.8. C Function Definition, Declaration and Use
  • 1.9. C Statement Style and Conventions
  • 1.10. Dynamic Logging
  • 1.11. Python Code
  • 1.12. Integrating with the Build System
• 2. Design
  • 2.1. Environment or Architecture-specific Sources
  • 2.2. Mbuf features
  • 2.3. Library Statistics
  • 2.4. PF and VF Considerations
• 3. ABI Policy
  • 3.1. Description
  • 3.2. General Guidelines
  • 3.3. The DPDK ABI policy
  • 3.4. New ABI versions
  • 3.5. Experimental
• 4. ABI Versioning
  • 4.1. What is a library’s soname?
  • 4.2. Major ABI versions
  • 4.3. Versioning Macros
  • 4.4. Running the ABI Validator
• 5. DPDK Documentation Guidelines
  • 5.1. Structure of the Documentation
  • 5.2. Role of the Documentation
  • 5.3. Building the Documentation
  • 5.4. Document Guidelines
  • 5.5. RST Guidelines
  • 5.6. Doxygen Guidelines
• 6. Contributing Code to DPDK
  • 6.1. The DPDK Development Process
  • 6.2. Source License
  • 6.3. Maintainers and Sub-trees
  • 6.4. Getting the Source Code
  • 6.5. Make your Changes
  • 6.6. Commit Messages: Subject Line
  • 6.7. Commit Messages: Body
  • 6.8. Creating Patches
  • 6.9. Checking the Patches
  • 6.10. Checking Compilation
  • 6.11. Checking ABI compatibility
  • 6.12. Sending Patches
  • 6.13. The Review Process
• 7. DPDK Vulnerability Management Process
  • 7.1. Scope
  • 7.2. Finding
  • 7.3. Report
  • 7.4. Confirmation
  • 7.5. CVE Request
  • 7.6. Fix Development and Review
  • 7.7. Pre-Release Disclosure
  • 7.8. Private Disclosure
  • 7.9. Public Disclosure
  • 7.10. References
• 8. DPDK Stable Releases and Long Term Support
  • 8.1. Introduction
  • 8.2. Stable Releases
  • 8.3. LTS Release
  • 8.4. What changes should be backported
  • 8.5. The Stable Mailing List
  • 8.6. Releasing
• 9. Patch Cheatsheet