Skip to content

Commit b7fc0c9

Browse files
committed
Fix formatting in Advanced Vulkan Compute conclusion section
Add missing blank lines after list introduction paragraphs to ensure proper Markdown rendering of bullet points in "Developing for advanced compute" and "Community and Resources" sections.
1 parent cc81a21 commit b7fc0c9

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

en/Advanced_Vulkan_Compute/conclusion.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ Throughout this series, we have explored the depths of modern GPU compute, movin
2323
If there is one takeaway from this series, it is this: **The GPU is not just a math coprocessor; it is a parallel throughput machine with its own complex hierarchy.**
2424

2525
Developing for advanced compute requires a shift in mindset:
26+
2627
- **Think in Waves**: Always look for opportunities to use subgroup (Wave) operations instead of workgroup-level barriers.
2728
- **Explicit Synchronization**: Don't rely on luck. Use the Vulkan Memory Model and Synchronization 2 to define exactly how and when data becomes visible.
2829
- **Data-First Design**: Design your data structures for the GPU's memory architecture (scalar layouts, LDS bank alignment) before you write a single line of logic.
@@ -39,6 +40,7 @@ The world of high-performance computing is vast. Now that you have a solid found
3940
== Community and Resources
4041

4142
As always, you are not alone in this journey. The Vulkan community is filled with experts and enthusiasts:
43+
4244
- **Khronos Slack/Discord**: Great for technical deep dives into specific extensions.
4345
- **Vulkan Specification**: Your ultimate source of truth for memory models and hardware constraints.
4446
- **Vendor-Specific Documentation**: Explore NVIDIA's Nsight, AMD's RGP, and Intel's GPA documentation for hardware-specific optimization tricks.

0 commit comments

Comments
 (0)