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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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:
> > On Tue, 2018-01-30 at 16:33 -0500, Laurence Oberman wrote:
> > > 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��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux