[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dfe76105-95a2-bd82-1f71-74b171b4a702@phrozen.org>
Date: Thu, 10 Aug 2017 10:10:27 +0200
From: John Crispin <john@...ozen.org>
To: Eric Dumazet <eric.dumazet@...il.com>,
David Miller <davem@...emloft.net>
Cc: andrew@...n.ch, f.fainelli@...il.com, muciri@...nmesh.com,
vivien.didelot@...oirfairelinux.com, netdev@...r.kernel.org,
sean.wang@...iatek.com, linux-kernel@...r.kernel.org,
shashidhar.lakkavalli@...nmesh.com,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH 0/4] net-next: dsa: fix flow dissection
On 10/08/17 08:42, Eric Dumazet wrote:
> 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
>
>
Hi Eric,
I have just sent the fix for this compile error
John
Powered by blists - more mailing lists