[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1502347335.4936.2.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Wed, 09 Aug 2017 23:42:15 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: David Miller <davem@...emloft.net>
Cc: john@...ozen.org, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
sean.wang@...iatek.com, netdev@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
muciri@...nmesh.com, shashidhar.lakkavalli@...nmesh.com
Subject: Re: [PATCH 0/4] net-next: dsa: fix flow dissection
On Wed, 2017-08-09 at 22:52 -0700, David Miller wrote:
> From: John Crispin <john@...ozen.org>
> Date: Wed, 9 Aug 2017 14:41:15 +0200
>
> > RPS and probably other kernel features are currently broken on some if not
> > all DSA devices. The root cause of this is that skb_hash will call the
> > flow_dissector. At this point the skb still contains the magic switch
> > header and the skb->protocol field is not set up to the correct 802.3
> > value yet. By the time the tag specific code is called, removing the header
> > and properly setting the protocol an invalid hash is already set. In the
> > case of the mt7530 this will result in all flows always having the same
> > hash.
> >
> > Changes since RFC:
> > * use a callback instead of static values
> > * add cover letter
>
> Series applied, thanks.
Is this related ?
net/core/flow_dissector.c: In function '__skb_flow_dissect':
net/core/flow_dissector.c:448:18: error: 'struct net_device' has no member named 'dsa_ptr'
ops = skb->dev->dsa_ptr->tag_ops;
^
make[3]: *** [net/core/flow_dissector.o] Error 1
Powered by blists - more mailing lists