On Mon, 28 Sep 2015, Jason Gunthorpe wrote: > I think your original idea of broadcast immediately and deferred > optimal mlid lookup is the best *functionally* for every case - only > when you enter the very edge world of caring about timing does it make > any difference.
Infiniband is about the edge. > Christoph's needs would probably be better served by giving some API > to control the mlid cache (ie the neightbour table is already 99% of > the way there). This would let some userspace component pre-load and > fix all relevant data and undesired cache activity simply can't add > jitter. Ok so on boot up we preload 3000 multicast groups into the neighbor table? What impact on IB performance would having such a number of mlid's in the cache have? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
