> On 14 Jan 2026, at 09:41, David Gwynne <[email protected]> wrote:
>
> my guess is the aq hardware wont do anything with the packets it's been
> asked to transmit while the link is down. a simple fix is to check the
> link state in the transmit path.
Some additional information here based on my testing today, if I set the
interface DOWN then it no longer consumes mbufs. It seems that the queueing
only occurs if the interface is UP but there is no carrier.
I can replicate this behaviour only if the interface is not populated on
startup, if I try to move the physical connection between the two interfaces
then the mbuf usage remains stable and after the interface has had something
connected it will not continue to consume mbufs. Although this could be due
to my misunderstanding exactly how this should work.
Either way I can reliably replicate this on aq1 by having aq0 connected and
aq1 never having a connection and simply bringing aq1 UP and DOWN.
