John Hurley wrote:
> On Thu, Jun 6, 2019 at 8:52 PM Florian Westphal wrote:
> >
> > David Miller wrote:
> > > From: Florian Westphal
> > > Date: Thu, 6 Jun 2019 14:58:18 +0200
> > >
> > > >> @@ -827,6 +828,7 @@ struct sk_buff {
> > > >>__u8tc_at_ingress:1;
> > > >>__
On Thu, Jun 6, 2019 at 8:52 PM Florian Westphal wrote:
>
> David Miller wrote:
> > From: Florian Westphal
> > Date: Thu, 6 Jun 2019 14:58:18 +0200
> >
> > >> @@ -827,6 +828,7 @@ struct sk_buff {
> > >>__u8tc_at_ingress:1;
> > >>__u8tc_redirected:1;
David Miller wrote:
> From: Florian Westphal
> Date: Thu, 6 Jun 2019 14:58:18 +0200
>
> >> @@ -827,6 +828,7 @@ struct sk_buff {
> >>__u8tc_at_ingress:1;
> >>__u8tc_redirected:1;
> >>__u8tc_from_ingress:1;
> >> + __u8
From: Florian Westphal
Date: Thu, 6 Jun 2019 14:58:18 +0200
>> @@ -827,6 +828,7 @@ struct sk_buff {
>> __u8tc_at_ingress:1;
>> __u8tc_redirected:1;
>> __u8tc_from_ingress:1;
>> +__u8tc_hop_count:2;
John Hurley wrote:
> On Thu, Jun 6, 2019 at 1:58 PM Florian Westphal wrote:
> > I dislike this, why can't we just use a pcpu counter?
> >
> > The only problem is with recursion/nesting; whenever we
> > hit something that queues the skb for later we're safe.
> >
>
> Hi Florian,
> The per cpu coun
On Thu, Jun 6, 2019 at 1:58 PM Florian Westphal wrote:
>
> John Hurley wrote:
> > TC hooks allow the application of filters and actions to packets at both
> > ingress and egress of the network stack. It is possible, with poor
> > configuration, that this can produce loops whereby an ingress hook
John Hurley wrote:
> TC hooks allow the application of filters and actions to packets at both
> ingress and egress of the network stack. It is possible, with poor
> configuration, that this can produce loops whereby an ingress hook calls
> a mirred egress action that has an egress hook that redire
TC hooks allow the application of filters and actions to packets at both
ingress and egress of the network stack. It is possible, with poor
configuration, that this can produce loops whereby an ingress hook calls
a mirred egress action that has an egress hook that redirects back to
the first ingres
