On Tue, 2018-01-30 at 15:02 -0700, Jason Gunthorpe wrote:
> On Tue, Jan 30, 2018 at 09:47:48PM +0000, Bart Van Assche wrote:
> > So apparently the ib_alloc_mr() fails sometimes (but not the first few times
> > it is called).
>
> Looks like the only way you can get that without hitting an kalloc
> oops print is if rxe_alloc() fails, and probably here:
>
> if (atomic_inc_return(&pool->num_elem) > pool->max_elem)
> goto out_put_pool;
>
> Suggesting srp hit the max # of mrs in rxe:
>
> RXE_MAX_MR = 2 * 1024,
>
> Or maybe we are now leaking mrs someplace?
>
> There is nothing accepted recently that mucks with this, still not
> seeing even a tenuous connection to any patches in the last few days
Hello Jason,
Since the number of memory regions that is allocated by the ib_srp driver
depends on the max_sect parameter in the login string I will start with
checking whether there have been any recent changes of that parameter in
the test script.
Thanks,
Bart.��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
