Re: [B.A.T.M.A.N.] [RFC v3 0/4] flow_dissector: Provide basic batman-adv unicast handling

2017-12-16 Thread Sven Eckelmann
On Freitag, 15. Dezember 2017 17:51:19 CET Willem de Bruijn wrote: [] > Thanks for making these changes. The flow dissection looks good to me. > > One possible issue is that this exposes kernel fixed width types u8/u16/.. > to userspace. For posix compatibility reasons, uapi headers use the >

Re: [RFC v3 0/4] flow_dissector: Provide basic batman-adv unicast handling

2017-12-15 Thread Willem de Bruijn
On Fri, Dec 15, 2017 at 1:23 PM, Sven Eckelmann wrote: > Hi, > > we are currently starting to use batman-adv as mesh protocol on multicore > embedded devices. These usually don't have a lot of CPU power per core but > are reasonable fast when using multiple cores. > > It was noticed that sending w

[RFC v3 0/4] flow_dissector: Provide basic batman-adv unicast handling

2017-12-15 Thread Sven Eckelmann
Hi, we are currently starting to use batman-adv as mesh protocol on multicore embedded devices. These usually don't have a lot of CPU power per core but are reasonable fast when using multiple cores. It was noticed that sending was working very well but receiving was basically only using on CPU c