Changes between Version 10 and Version 11 of WARPLab/Requirements

Timestamp:

Aug 27, 2013, 9:54:03 AM (11 years ago)

Author:

murphpo

Comment:

--

WARPLab/Requirements

@@ -24 +24 @@
   * Open firewall for UDP ports (10000 and [9000:9000+numNodes-1])
 
-----
 
-== Using Jumbo Ethernet Frames ==
+= Using Jumbo Ethernet Frames =
 The WARP hardware design supports Ethernet packets up to 9000 bytes. Any Ethernet packet larger than 1500 bytes is considered a "jumbo frame" and support for these jumbo frames among consumer NICs and switches is limited. To see if your hardware supports jumbo frames, increase the MTU setting on your computer to the maximum allowed setting. Then, two tests can determine the maximum usable payload: (a) a ping test, and (b) a WARPLab test.
 ----
-==== Ping Test ====
+== Ping Max Payload Test ==
 Once the MTU on your machine is raised to its maximum, you can use pings from your computer to determine whether your switch and NIC can actually send and receive jumbo frames. Make sure you have a board configured with the WARPLab bitstream and a DIP switch of '0' (making its IP address 10.0.0.1).
 
@@ -81 +80 @@
 8008 bytes from 10.0.0.1: icmp_seq=1 ttl=32 time=3.071 ms
 }}}
-----
-==== WARPLab Test ====
+
+== WARPLab Max Payload Test ==
 If the ping test indicates that your PC and your Ethernet switch support jumbo frames, the next step is to see if WARPLab works with jumbo frames. When node objects are first set up in a WARPLab script, they run a test with their associated boards to see what maximum payload size can be supported. First, re-run the [wiki:../Reference/Utility#wl_setup 'wl_setup'] function in {{{M_Code_Reference}}} and select that you would like to enable jumbo frame support. Next, ensure one WARP board is programmed with the WARPLab bitstream and configured with DIP switch '0'. Then, copy and paste the following lines to the MATLAB command line:
 
@@ -93 +92 @@
 This will display the payload size the WARPLab has configured itself to use. For one of our PCs, this value returns as {{{8960}}}, showing the jumbo frame support is correctly working.
 
-[[br]]
-== Hardware Compatibility ==
+== Jumbo Frame Hardware Compatibility ==
 
-It is impossible to form a definitive list of hardware that is compatible with jumbo frame support, but we will maintain a list of observed setups and their compatibility. If you try jumbo frames and have a hardware setup that does or does not work with them, please post to [http://warpproject.org/forums/ the WARP forums] so we can add them to the list.
+Support for jumbo frames varies widely across Ethernet NICs, PCs and OSs. Our observations for a variety of hardware/OS combinations are described below. If you try jumbo frames and have a hardware setup that does or does not work with them, please post to [http://warpproject.org/forums/ the WARP forums] so we can add them to the list.
 
 '''Known Compatible:'''
@@ -104 +102 @@
 '''Known Partially Compatible:'''
  * Apple 2013 Macbook Pro, OSX 10.8.3, Apple Thunderbolt to Gigabit Ethernet Adapter
-  * Appears to have a "hidden" MTU maximum around 8000, despite the GUI letting you choose 9000.
+  * Appears to have a "hidden" MTU maximum around 8000 (despite the GUI letting you choose 9000)
  * Apple 2011 Mac Mini, OSX 10.8.3, Broadcom 57765-B0
-  * Appears to work for MTU < 7000. There were problems with larger MTUs, but those problems may be attributed to a bad switch.
+  * Appears to work for MTU < 7000
 
 '''Known Incompatible:'''
- * Dell workstation, Windows 7 64-bit, Broadcom NetXtreme Gigabit Ethernet BCM5755
- * Apple 2010 Macbook Pro, OSX 10.8.3, Broadcom 5764-B0
-
-[[br]]
+ * Ethernet NIC using the Broadcom BCM5755 controller
+ * Apple 2010 Macbook Pro using the Broadcom 5764-B0 controller