From: Cong Wang
Date: Sat, 11 Jun 2016 17:14:09 -0700
> On Sat, Jun 11, 2016 at 3:54 PM, David Miller wrote:
>> From: Florian Westphal
>> Date: Sat, 11 Jun 2016 12:46:04 +0200
>>
>>> sch_atm returns this when TC_ACT_SHOT classification occurs.
>>>
>>> But all other schedulers that use tc_classi
On Sat, Jun 11, 2016 at 3:54 PM, David Miller wrote:
> From: Florian Westphal
> Date: Sat, 11 Jun 2016 12:46:04 +0200
>
>> sch_atm returns this when TC_ACT_SHOT classification occurs.
>>
>> But all other schedulers that use tc_classify
>> (htb, hfsc, drr, fq_codel ...) return NET_XMIT_SUCCESS | _
David Miller wrote:
> From: Florian Westphal
> Date: Sat, 11 Jun 2016 12:46:04 +0200
>
> > sch_atm returns this when TC_ACT_SHOT classification occurs.
> >
> > But all other schedulers that use tc_classify
> > (htb, hfsc, drr, fq_codel ...) return NET_XMIT_SUCCESS | __BYPASS
> > in this case so
From: Florian Westphal
Date: Sat, 11 Jun 2016 12:46:04 +0200
> sch_atm returns this when TC_ACT_SHOT classification occurs.
>
> But all other schedulers that use tc_classify
> (htb, hfsc, drr, fq_codel ...) return NET_XMIT_SUCCESS | __BYPASS
> in this case so just do that in atm.
Yes, but it's
sch_atm returns this when TC_ACT_SHOT classification occurs.
But all other schedulers that use tc_classify
(htb, hfsc, drr, fq_codel ...) return NET_XMIT_SUCCESS | __BYPASS
in this case so just do that in atm.
BATMAN uses it as an intermediate return value to signal
forwarding vs. buffering, but
