From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Wise Subject: Re: sense remote hardware address change by rdma-cm applications Date: Tue, 20 Jul 2010 16:15:22 -0500 Message-ID: <4C4611EA.6000700@opengridcomputing.com> References: <20100720001436.GH7920@obsidianresearch.com> <4C454F80.1060808@Voltaire.com> <4C45E701.7030501@opengridcomputing.com> <20100720184620.GJ7920@obsidianresearch.com> <4C45F6F5.6050008@opengridcomputing.com> <20100720203044.GK7920@obsidianresearch.com> <4C460BFD.5010707@opengridcomputing.com> <20100720205746.GL7920@obsidianresearch.com> <4C460F08.7030304@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C460F08.7030304-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jason Gunthorpe Cc: Or Gerlitz , Sean Hefty , linux-rdma , "Tung, Chien Tin" List-Id: linux-rdma@vger.kernel.org Steve Wise wrote: > Jason Gunthorpe wrote: >> On Tue, Jul 20, 2010 at 03:50:05PM -0500, Steve Wise wrote: >> >> >>>> I think if RDMACM manages the dst and lets the devices access it then >>>> all the existing netdev infrastructure for poking at a dst should be >>>> available to the device? >>>> >>> Yes. But I'm not sure exactly how the logic I described previous >>> for cxgb* would be handled in the design being ironed out here. >>> >> >> I'm thinking something like this.. >> >> - The RDMA CM gets the dst from its route lookup locks it and stores >> it. >> - Instead of doing a route lookup cxgb gets the dst from RDMA CM, >> locks it and stores it >> - RDMA CM traps all notifications/etc and generates callback to cxgb >> to say the dst has changed. >> - cxgb releases the old dst and grabs the new one, updates the HW, >> etc. >> >> Basically the same as what you have now, but all the logic to find >> and monitor the dst moves to RDMA CM.. >> >> redirects/etc are all handled by netdev/rdma cm and just generate the >> same 'dst has changed' call back to cxgb.. >> >> Or's user space notification stuff hooks the same callback to generate >> a notification to userspace about the new dst. >> >> All the stuff you do now with the dst you can keep doing, you just >> remove all the route lookup and netdev hooking to get the dst from >> RDMA CM. >> >> Jason >> > > Sounds like this would work nicely. > > > Steve. > Need to hear from Intel. CCing Chien. -- 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