Thread (3 messages) 3 messages, 2 authors, 2013-02-03

Re: [PATCH net-next 1/2] cxgb4: Send Flush Work Request on a TX Queue

From: David Miller <davem@davemloft.net>
Date: 2013-02-03 04:04:48

From: Vipul Pandya <redacted>
Date: Thu, 31 Jan 2013 19:36:26 +0530
Send Flush Work Request on a TX Queue if it has unreclaimed TX Descriptors
and the last time anything was sent on the associated net device was more than
5 seconds in the past, issue a flush request on the TX Queue in order to get
any stranded skb's off the TX Queue.

Signed-off-by: Jay Hernandez <redacted>
Signed-off-by: Vipul Pandya <redacted>
Is the "TX finished" event reporting mechanism supported by this chip
so broken that you cannot use that instead?

Timers and deferred logic to reclaim TX entries is terrible for the
Linux stack.  It means that socket reclaim is delayed, it means that
you really cannot support byte queue limits, it means that TCP Small
Queues won't work properly, it means that packet schedulers can
measure traffic in a wildly inaccurate manner, and so on and so forth.

I'd rather you guys fix these TX reclaim issues properly, rather
than continuing to paper over them with hacks.  A 5 second delay
on TX packet reclaim is absolutely not acceptable.

I'm not applying these two patches, sorry.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help