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. C Indentation
  • 1.7. C Function Definition, Declaration and Use
  • 1.8. C Statement Style and Conventions
  • 1.9. Dynamic Logging
  • 1.10. Python Code
  • 1.11. Integrating with the Build System
• 2. Design
  • 2.1. Environment or Architecture-specific Sources
  • 2.2. Library Statistics
  • 2.3. PF and VF Considerations
• 3. DPDK ABI/API policy
  • 3.1. Description
  • 3.2. General Guidelines
  • 3.3. ABI/API Deprecation
  • 3.4. Experimental APIs
  • 3.5. Library versioning
  • 3.6. ABI versioning
  • 3.7. Running the ABI Validator
• 4. DPDK Documentation Guidelines
  • 4.1. Structure of the Documentation
  • 4.2. Role of the Documentation
  • 4.3. Building the Documentation
  • 4.4. Document Guidelines
  • 4.5. RST Guidelines
  • 4.6. Doxygen Guidelines
• 5. Contributing Code to DPDK
  • 5.1. The DPDK Development Process
  • 5.2. Source License
  • 5.3. Maintainers and Sub-trees
  • 5.4. Getting the Source Code
  • 5.5. Make your Changes
  • 5.6. Commit Messages: Subject Line
  • 5.7. Commit Messages: Body
  • 5.8. Creating Patches
  • 5.9. Checking the Patches
  • 5.10. Checking Compilation
  • 5.11. Sending Patches
  • 5.12. The Review Process
• 6. DPDK Vulnerability Management Process
  • 6.1. Scope
  • 6.2. Finding
  • 6.3. Report
  • 6.4. Confirmation
  • 6.5. CVE Request
  • 6.6. Fix Development and Review
  • 6.7. Pre-Release Disclosure
  • 6.8. Private Disclosure
  • 6.9. Public Disclosure
  • 6.10. References
• 7. DPDK Stable Releases and Long Term Support
  • 7.1. Introduction
  • 7.2. Stable Releases
  • 7.3. LTS Release
  • 7.4. What changes should be backported
  • 7.5. The Stable Mailing List
  • 7.6. Releasing
  • 7.7. ABI
• 8. Patch Cheatsheet