[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.
Hearns, John john.hearns at mclaren.comMon Oct 26 10:03:27 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 ]
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, and clash with the IPMI ports (ie your rsh session disappears down a big hole). And before anyone says it - more modern kernels raise the sun rpc min reserved port to above the IPMI port(s) The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error you should not copy it, retransmit it, use it or disclose its contents but should return it to the sender immediately and delete your copy.
- 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
