Re: how to debug (mlx4) CQ overrun

Wendy Cheng
2011-10-08T11:21:06Z

On Fri, Sep 23, 2011 at 2:30 PM, Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> wrote:

> There are not really any tools, but this is usually straightforward to
> look at from your app.
>

Great thanks for the response. It helped (to ensure our cq handling
logic was ok). The issue turns out to be build related. After doing a
clean rebuild of OFED IB modules with the modified header files, the
problem went away. The (header file) change was a result of exporting
kernel FMR (fast memory registration) to user space for an
experimental project.

Again, thank you for the write-up. It is very appreciated.

-- Wendy