On Wed, Oct 28, 2009 at 04:49:28PM +0200, Or Gerlitz wrote: > Jason Gunthorpe wrote: > > **COMPILE TESTED ONLY** > > any reason why other people have to test for you?
Just a preliminary proposal - other people can do whatever they want. Look at the list of things it fixes and decide your self if you want to help or not <shrug> > > Convert the address resolution process for outgoing connections > > to be very similar to the way the TCP stack does the same operations. > > This fixes many corner case bugs that can crop up. > > rdma_join_multicast(3) states that "before joining a multicast > group, the rdma_cm_id must be bound to an RDMA device by calling > rdma_bind_addr or rdma_resolve_addr", please make sure that this > flow isn't broken by your patch. Can you explain how rdma_resolve_addr is used in conjunction with multicast? I do not understand what the dest would be. Is it just a man page typo? I belive the rdma_bind_addr path is unaffected. Jason -- 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
