On Fri, May 17, 2013 at 10:36 PM, Jack Wang wrote:
> We've seen below neigh->list list corruption warning during testing,
So about little heads up on what kernel you are using? what's the way
to trigger this warning?
> From Dongsu's and my opinion, several place also need
> netif_tx_lock(_bh)/n
On 2013年05月18日 21:37, Or Gerlitz wrote:
> On Fri, May 17, 2013 at 10:36 PM, Jack Wang
> wrote:
>> We've seen below neigh->list list corruption warning during testing,
>
> So about little heads up on what kernel you are using? what's the way
> to trigger this warning?
Hi Or,
I tried 3.4.23, and
On 19/05/2013 00:36, Jack Wang wrote:
I tried 3.4.23, and mainline kernel from Roland's rdma-for-linus, we
added bug injection interface, run multithread iperf, and switched ib
mode between connected and datagram in sync on each side as Shlomo
suggested.
Can you be more specific re the bug in
On 18/05/2013 00:37, Roland Dreier wrote:
you see that when freeing a CQ, we first do the HW2SW_CQ firmware
command; once this command completes, no more events will be generated
for that CQ. Then we do synchronize_irq for the CQ's interrupt
vector. Once that completes, no more completion handl
