Thread (1 message) 1 message, 1 author, 2018-01-30

Re: [PATCH rdma-next v7 0/8] RDMA resource tracking

From: Bart Van Assche <hidden>
Date: 2018-01-30 21:47:48

On Tue, 2018-01-30 at 14:42 -0700, Jason Gunthorpe wrote:
On Tue, Jan 30, 2018 at 09:40:14PM +0000, Bart Van Assche wrote:
quoted
On Tue, 2018-01-30 at 16:33 -0500, Laurence Oberman wrote:
quoted
Can I take your tree and see if this fails for me too,
Your last tree was fine, so did not have this latest stuff.
Can I just pull to what I have
Hello Laurence,

So far I have seen this behavior only inside a VM but not yet on a system
with more memory than the VM. This issue may be specific to the memory size
of the VM. I think we should try to isolate furhter what caused this before
trying to reproduce it on more setups.
Did you get an oops print related a kalloc failure?

Or am I wrong and the ENOMEM is coming from someplace else?
Hello Jason,

I just noticed the following in the system log:

Jan 30 12:53:15 ubuntu-vm kernel: ib_srp: rxe0: ib_alloc_mr() failed. Try to reduce max_cmd_per_lun, max_sect or ch_count

So apparently the ib_alloc_mr() fails sometimes (but not the first few times
it is called).

Thanks,

Bart.�{.n�+�������+%��lzwm��b�맲��r��zX��ݙ�����ܨ}���Ơz�&j:+v����n�r��6;靫3��\
nnX��f�z��2�ޙ���&�)ߡ�a����
�G���h��j:+v���w�٥
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help