On Wed, Jan 24, 2018 at 01:01:58AM -0700, Nicholas A. Bellinger wrote: > Hi Shiraz & Co, > > Thanks for the feedback. > > On Mon, 2018-01-22 at 17:49 +0000, Saleem, Shiraz wrote: > > > Subject: Re: SQ overflow seen running isert traffic with high block sizes > > > > > > > > > First, would it be helpful to limit maximum payload size per I/O for consumers > > > based on number of iser-target sq hw sges..? > > > > > Assuming data is not able to be fast registered as if virtually contiguous; > > artificially limiting the data size might not be the best solution. > > > > But max SGEs does need to be exposed higher. Somewhere in the stack, > > there might need to be multiple WRs submitted or data copied. > > > > Sagi..? > > > For reference, what is i40iw's max_send_sg reporting..? 3 > > Is max_data_sg_nents=32 + 4k pages = 128K the largest MAX TRANSFER > LENGTH to avoid consistent SQ overflow as-is with i40iw..? For the configuration I am testing, max_data_sg_nents=32 & 64 worked, and the SQ overflow issue reproduced at 128. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
