> + /* > + * Add room for frmr register and invalidate WRs > + * Requests sometimes have two chunks, each chunk > + * requires to have different frmr. The safest > + * WRs required are max_send_wr * 6; however, we > + * get send completions and poll fast enough, it > + * is pretty safe to have max_send_wr * 4. > + */ > + ep->rep_attr.cap.max_send_wr *= 4;
Seems like a bad design if there is a possibility of work queue overflow; if you're counting on events occurring in a particular order or completions being handled "fast enough", then your design is going to fail in some high load situations, which I don't think you want. - R. -- Roland Dreier <rola...@cisco.com> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
