RE: NFSoRDMA Fails for max_sge Less Than 18

["Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>]

> >>
> >>> (haven't looked in detail at your patches...sorry).  Our QA ran
testing on
> > 4.9
> >>> and didn't see this issue, so that's why I'm asking.    They have not
yet
> > run
> >>> NFS/RDMA testing on 4.9-rc.  I've asked them to do a quick regression
> test
> > asap.
> >>
> >
> > Correction: I meant 4.10-rc above.
> >
> > But still, I believe Chelsio tested 4.9, so perhaps it isn't the "mount"
that
> > causes a failure but trying to send something with an SGE > 4 that
happens
> > immediately after the mount?  And since cxgb4 supports up to 17, the
> failure
> > wouldn't be seen until some inline message was attempted that required
> 18
> > sges...
> 
> The original check for 18 or 19 was too aggressive (that's the
> bug here). With the default inline threshold settings, RPC-over-RDMA
> won't ever use more than 4 (or at most 5) SGEs for RDMA Send.
> 
> So if somehow the mount was allowed, and no changes were made to the
> default settings, everything should still work fine for cxgb4.
> 

Hey Chuck, Chelsio confirmed mounts fail with 4.10-rc.  So can you get a fix
in 4.10-rc (and back to 4.9 if the regression is there) to ensure at least a
max_sge of 4 is supported? 

Steveo


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html