|SUCCESS| event/cnxk: fix new-event burst enqueue with LMTST

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/172718

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-11-07

# DPDK Patch Review

## ERRORS

None.

## WARNINGS

None.

## INFO

### Early Return Path Correctness

The added early-return paths (lines checking `nb_events < BIT(ROC_SSO_AW_PER_LMT_LINE_LOG2)`) enqueue events one-by-one and return early if `cn10k_sso_hws_new_event()` or `cn20k_sso_hws_new_event()` returns false (failure).

The original LMTST path below does **not** have a fallback when individual event enqueue fails -- it submits all events via LMTST without per-event error checking. This difference in behavior (early return on first failure vs. attempting all events) is intentional and acceptable: the small-burst optimization is choosing a different trade-off.

No action required; noting for completeness.

### Barrier Placement

The `rte_io_wmb()` is placed immediately after the LMTST submissions and before the `left` check. This ensures that all stores in the current iteration are visible before the next iteration begins or the function returns.

The barrier is correctly an I/O barrier (`rte_io_wmb()`) rather than a thread fence, as it orders writes to device MMIO (LMTST target addresses). No issue here.

### Threshold Selection

The threshold `BIT(ROC_SSO_AW_PER_LMT_LINE_LOG2)` is presumably derived from hardware LMTST line capacity. The patch description states "small bursts, below one LMT line of entries" should bypass LMTST, which aligns with this threshold.

Assuming `ROC_SSO_AW_PER_LMT_LINE_LOG2` is defined consistently with the hardware limit, this is correct. No issue found in the patch itself; the macro definition is outside the diff.

---

**Summary:** The patch adds an I/O write barrier to order LMTST stores across loop iterations and introduces a small-burst fast path that bypasses LMTST for sub-threshold counts. Both changes are correctness fixes with clear intent. No errors or warnings identified.

Review-Result: CLEAN