summaryrefslogtreecommitdiffstats
path: root/sys/netipx
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2012-03-29 17:39:18 +0000
committeradrian <adrian@FreeBSD.org>2012-03-29 17:39:18 +0000
commit9cb839a32c6a135485c4573a69c278031667e9c5 (patch)
treeecdb2e62cc341a90ea775e7e5b017085c860a417 /sys/netipx
parentc56f63e2badce01fac17bc5a106216ed15fcd003 (diff)
downloadFreeBSD-src-9cb839a32c6a135485c4573a69c278031667e9c5.zip
FreeBSD-src-9cb839a32c6a135485c4573a69c278031667e9c5.tar.gz
Defer the rescheduling of TID -> TXQ frames in some instances.
Right now ath_txq_sched() is mainly called from the TX ath_tx_processq() routine, which is (mostly) done as part of the taskqueue. It shouldn't be called outside the taskqueue. But now that I'm about to flip back on BAR TX, I'm going to start stressing the ath_tx_tid_pause() and ath_tx_tid_resume() paths. What I don't want to have happen is a reschedule of the TID traffic _during_ the completion of TX frames. Ideally I'd like to have a way to flag back up to the processing code that the current hardware queue should be rechecked for software TID queue frames. But for now, this should suffice for the BAR TX case. I may eventually delete this code once I've brought some further sanity to the general TX queue/completion path.
Diffstat (limited to 'sys/netipx')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud