[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.
Bogdan Costescu bcostescu at gmail.comMon Oct 26 09:53:11 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 5:23 PM, Mark Hahn <hahn at mcmaster.ca> wrote: > it's surprising that it works at all, since there's no real > standard for sharing the hardware. I don't think that a standard is actually needed... My naive understanding is that the NIC firmware does packet inspection (no need for deep packet inspection, only MAC and IP headers are enough) and doesn't allow the main system to see that there is a packet if the packet had the BMC as the destination and doesn't allow the BMC to see that there is a packet if the packet had the main system as the destination. Then both the main system and the BMC can use the same way of accessing the NIC, as documented by the NIC vendor - no standard required. Hmmm, actually re-reading what I just wrote, sounds too good to be true so I might miss something :-) -- Bogdan
- 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
