> From: Long Li <[email protected]> > > The HWC starts with depth-one bootstrap queues. Treat the PF-reported depth > as a maximum and rebuild the channel exactly for reports from 2 through > 128. Keep the untouched bootstrap queues for depth one and reports above > 128, and require a rebuilt channel to repeat the selected depth. > > Treat the reported request and response sizes as directional maxima. > Rebuild only when both reports equal the 4096-byte bootstrap allocation, > then enforce the effective report/allocation limit on every request and > expected response. > > Keep each candidate channel private through queue creation, establishment > and the direct EQ test. Publish only the final tested channel. If a rebuild > fails after acknowledged teardown, destroy that candidate and establish > [ ... ] > goto-heavy creation flow from v5. > > Link: https://lore.kernel.org/r/[email protected] > Signed-off-by: Long Li <[email protected]> > Signed-off-by: Wei Hu <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review ยท https://sashiko.dev/#/patchset/[email protected]?part=4
