[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpV-LGNp=jBvFKhz50FtcYUpU5eCY8L853oWRFVoSqUPjA@mail.gmail.com>
Date: Sun, 17 May 2020 11:42:04 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Taehee Yoo <ap420073@...il.com>, Netdev <netdev@...r.kernel.org>,
syzbot <syzbot+aaa6fa4949cc5d9b7b25@...kaller.appspotmail.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [Patch net-next v2 1/2] net: partially revert dynamic lockdep key changes
On Sat, May 16, 2020 at 9:53 AM Vladimir Oltean <olteanv@...il.com> wrote:
> Thanks a lot for presenting the options. In general, xmit in DSA is
> relatively simple and most of the time stateless. My stacked DSA setup
> appears to work just fine with NETIF_F_LLTX, including the updating of
> percpu counters. I'm not really sure if there's something in
> particular to test?
> Anyway, will you send a patch with NETIF_F_LLTX or should I do it? I
> can do further testing if necessary.
If DSA is software based, there is a large chance it can be just
using NETIF_F_LLTX, like you said.
Please do send a patch for this NETIF_F_LLTX. Note my patch
simply reverts to the old code, this issue probably exists before it.
Thanks!
Powered by blists - more mailing lists