If toy are using PVM or similar technologies, would'nt the best route to be to pick a transport that is the fastest. Last thing you want is messages to be bogged down in transport.
I"m nut sure what type of clusters you are building but I would say use multiple interfaces. If you are stuck with 1U per node, use a multi-port NIC. I have a D-Link card that as 4 interfaces on one flange. If you are stuck to blade servers, I'm not sure what to do other than place them all on a private back bone. Then have one brain that could be a gateway to them and the main network. I would stay away from message passing over slow links. You could use the firewall for heartbeat. On Wed, 2003-03-05 at 09:32, David Leimbach wrote: > True... I guess I didn't state my case clearly enough that I think IP > over firewire > is in itself a good thing for clusters. > > ppp connections with it are fine too but not very useful for my line of > work > which is parallel computing middleware :) > > Dave > On Wednesday, March 5, 2003, at 08:30 AM, Christopher Fowler wrote: > > > The beauty of ppp is that you have support in the kernel to do it. > > Else, you are stuck to writing some type of interface driver for the > > kernel. In the short term, this may not be a workable solution. > > > > On a side note, > > > > I read an article on /. about using firewire + MinDV for backup. I > > guess I can get some use out of my camera after all. > > > > Chris > > > > On Wed, 2003-03-05 at 09:21, David Leimbach wrote: > >> Yeah... point to point connections are interesting and powerful but IP > >> would > >> be better if we could get it. > >> > >> I wish I knew more about how to implement it. :) > >> > >> Dave > >> On Wednesday, March 5, 2003, at 08:23 AM, Christopher Fowler wrote: > >> > >>> This may not be a workable solution, but if you can get 2 programs to > >>> send data across the firewire to one another, you could use pppd > >>> through > >>> that tunnel. > >>> > >>> > >>> On Wed, 2003-03-05 at 08:25, David Leimbach wrote: > >>>> Interesting... I didn't even know we had Ethernet over firewire :). > >>>> > >>>> Mac OS X and Windows XP both have IP over firewire either working or > >>>> in the works and somewhat usable. The only one I can claim any > >>>> experience > >>>> with is Mac OS X. It's somewhat flaky though and you get unreliable > >>>> spikes > >>>> in some basic performance tests I have done with it. > >>>> > >>>> It would be a really interesting value added feature for FreeBSD 5.x > >>>> and could potentially open FBSD up even more to the "cluster" market > >>>> which is somewhere its not as proliferated as linux. > >>>> > >>>> With the advent of firewire2 on the horizon it may be even more > >>>> impressive. > >>>> > >>>> I believe there is even an Oracle product for linux which can > >>>> cluster > >>>> databases > >>>> over firewire now. [I don't know if its IP though] > >>>> > >>>> > >>>> Dave > >>>> On Wednesday, March 5, 2003, at 01:43 AM, Rossam Souza Silva wrote: > >>>> > >>>>> > >>>>> Hi, there is some plan to port NetBSD's implementation of IP over > >>>>> Firewire? I know, we have "Ethernet over Firewire", but like the > >>>>> Linux > >>>>> one, isn't a standard... > >>>>> > >>>>> Just curious. > >>>>> > >>>>> ------------------------------------------------------------------- > >>>>> -- > >>>>> -- > >>>>> ------- > >>>>> (_ ) "Contrary to popular belief, UNIX is user friendly. It > >>>>> just > >>>>> happens > >>>>> \\\'',) ^ to be very selective about who it decides to make > >>>>> friends > >>>>> with." > >>>>> \/ \( > >>>>> .\._/_) Rossam Souza Silva ([EMAIL PROTECTED]) > >>>>> ------------------------------------------------------------------- > >>>>> -- > >>>>> -- > >>>>> ------ > >>>>> > >>>>> > >>>>> To Unsubscribe: send mail to [EMAIL PROTECTED] > >>>>> with "unsubscribe freebsd-current" in the body of the message > >>>> > >>>> > >>>> To Unsubscribe: send mail to [EMAIL PROTECTED] > >>>> with "unsubscribe freebsd-current" in the body of the message > >>> > >>> > >> > >> > >> To Unsubscribe: send mail to [EMAIL PROTECTED] > >> with "unsubscribe freebsd-current" in the body of the message > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
