nvme-fabrics: crash at nvme connect-all

Steve Wise swise at opengridcomputing.com
Thu Jun 9 06:27:45 PDT 2016


> 
> >> Which device are you using? Are you running on a low memory machine?
> >> Perhaps the rdma rw code needs to check max_mr capability?
> >>
> >
> > It's a rather big machine with 8 cores/16GB of memory, never had memory
> > limitation problems on this one. The card is a Chelsio T5. One of the
> > targets of this configuration is to check if it works with this card.
> 
> So it must come from the Chelsio device then...
> 
> Can you provide the max_mr output of the device (you can use
> ibv_devinfo -v from libibverbs/ibverbs-utils).
> 
> What happens if you use smaller queues, say 64/32 (can be added as a
> queue_size parameter working directly from sysfs, nvme-cli does not
> support this yet).
> 
> Steve, did you see this before? I'm wandering if we need some sort
> of logic handling with resource limitation in iWARP (global mrs pool...)

Haven't seen this.  Does 'cat /sys/kernel/debug/iw_cxgb4/blah/stats' show anything interesting?  Where/why is it crashing? 




More information about the Linux-nvme mailing list