Hi, Am Montag, dem 17.11.2025 um 09:39 +0200 schrieb Shani Peretz: > Offending commit added rxq_ctrl->mtu to track MTU at queue > allocation time for validating shared RX queue compatibility. > > When MTU changes via rte_eth_dev_set_mtu(), only priv->mtu was > updated, leaving rxq_ctrl->mtu with the old value.
If you read the commit message of the offending patch, this was in fact intentional. The MTU at allocation time is relevant when joining a Rx share group, as it is (to the best of my knowledge) the only MTU setting that actually has an influence on the size of the packet buffers. Therefore, it is the value which is relevant for sharing packet buffers. I've tested your patch again with the prototype I used to discover the original bug and unfortunately it reappears. Best regards, Adrian -- Adrian Schollmeyer SysEleven GmbH Boxhagener Straße 80 10245 Berlin T +49 30 / 23 32 012-0 F +49 30 / 61 67 55 5-0 https://www.syseleven.de https://www.linkedin.com/company/syseleven-gmbh Current system status always at: https://www.syseleven-status.net/ Company headquarters: Berlin Registered court: AG Berlin Charlottenburg, HRB 108571 Berlin Managing directors: Andreas Hermann, Jens Ihlenfeld, Jens Plogsties, Andreas Rückriegel
signature.asc
Description: This is a digitally signed message part
