Download raw body.
now with DSCP_VA (was Re: update ieee80211_classify() for more responsive SSH)
update ieee80211_classify() for more responsive SSH
I have a worry that as soon as our kernel does conversion from one priority classification, to a different level's priority conversion, we should possibly be responsible for doing some traffic management automatically. My gut feeling is we should be the same rate limiting back-pressure that downstream devices do. If we don't have that... hey, can I get a trivial knob to make my chrome set the DSCP_EF flag? Or can we make that the default? See, I'm saying there is a slippery slope to EF becoming the default, and I feel like that should be stopped by saying high priority obviously means a limited % of traffic on the port.
now with DSCP_VA (was Re: update ieee80211_classify() for more responsive SSH)
update ieee80211_classify() for more responsive SSH