> > > Under heavy TX load, bnx2x_poll() can loop forever and trigger soft lockup
> bugs.
> > >
> > > A napi poll handler must yield after one TX completion round, risk
> > > of livelock is too high otherwise.
> > >
> > > Bug is very easy to trigger using a debug build, and udp flood,
> > > because
From: Eric Dumazet
Date: Tue, 08 Dec 2015 05:54:40 -0800
> From: Eric Dumazet
>
> Under heavy TX load, bnx2x_poll() can loop forever and trigger
> soft lockup bugs.
>
> A napi poll handler must yield after one TX completion round,
> risk of livelock is too high otherwise.
>
> Bug is very easy
On Tue, 2015-12-08 at 17:02 +, Yuval Mintz wrote:
> > Under heavy TX load, bnx2x_poll() can loop forever and trigger soft lockup
> > bugs.
> >
> > A napi poll handler must yield after one TX completion round, risk of
> > livelock is
> > too high otherwise.
> >
> > Bug is very easy to trigge
> Under heavy TX load, bnx2x_poll() can loop forever and trigger soft lockup
> bugs.
>
> A napi poll handler must yield after one TX completion round, risk of
> livelock is
> too high otherwise.
>
> Bug is very easy to trigger using a debug build, and udp flood, because of
> added
> cpu cycles
From: Eric Dumazet
Under heavy TX load, bnx2x_poll() can loop forever and trigger
soft lockup bugs.
A napi poll handler must yield after one TX completion round,
risk of livelock is too high otherwise.
Bug is very easy to trigger using a debug build, and udp flood, because
of added cpu cycles i