[Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Rahul Nabar rpnabar at gmail.comMon Oct 26 10:15:01 PDT 2009
- Previous message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Next message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Oct 26, 2009 at 12:03 PM, Hearns, John <john.hearns at mclaren.com> wrote: > I don't think that a standard is actually needed... My naive > understanding is that the NIC firmware does packet inspection > > As I just said, I thought there was a bridge chip before the NIC, > and I agree there is packet filtering. > Look up my tortuous examination of what happens when you run a lot of > 'rsh'sessions on a cluster, John, you talked about this problem once before but I couldn't find the relevant thread. I was curious to read about it. Do you have a link to the thread or can you redump your analysis in this one? Thanks! -- Rahul
- Previous message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Next message: [Beowulf] any creative ways to crash Linux?: does a shared NIC IMPI always remain responsive?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
