On Wed, 2006-07-05 at 20:03 -0700, David Miller wrote: > From: Roland Dreier <[EMAIL PROTECTED]> > Date: Wed, 05 Jul 2006 13:29:35 -0700 > > > The way forward seems to be to merge basic iWARP support that lives in > > drivers/infiniband, and then you can accept or reject things for > > better integration, like notifiers for routing changes. > > <sarcasm> > Let's merge in drivers before the necessary infrastructure. > </sarcasm> > > No, I think that's not the way forward. You build the foundation > before the house, if the foundation cannot be built then you are > wasting your time with the house idea.
We have been running NFS and other apps over iWARP 24x7 for the last 6 mos...without the proposed netdev patch. We've run 200+ node MPI clusters for days and days over iWARP...without the proposed netdev patch. We ran iWARP interoperability tests across the country between Boston and San Jose...without ... yes I know ... you get it. <sarcasm> News flash...the foundation is built! </sarcasm> But! Our stable LAN and the WAN tests didn't often experience MTU changes, and redirects...but of course we knew these were inevitable. So our goal was to make iWARP more robust in the face of a more dynamic network topology. Shutters on the house maybe...I dunno, it's your analogy ;-) All that said, the proposed patch helps not only iWARP, but other transports (iSCSI, IB) as well. It is not large, invasive, intrusive...hell it's not even new. It leverages an existing event notifier mechanism. This patch is about dotting I's and crossing T's, it's not about foundations. > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
