twitch_ethtune
--------------
This is the service and puppet module to manage ethtool settings via a config file.
ethtune supports all the same ethtool setting managed via the interfaces file and
utilizes ethtool's own if-up hook script.

How does ethtune work?
ethtune will parse its config and apply the ethtool settings on boot or the config
file has been changed. ethtune supports all the same ethtool settings as you would
find in the interfaces file. See /usr/share/doc/ethtool/README.Debian for
supported options.

How to use in puppet?

twitch_ethtune::settings:
  hardware-dma-ring-rx: 2048
  hardware-irq-coalesce-rx-usecs: 1

or

class { 'twitch_ethtune':
  settings => {
    hardware-dma-ring-rx => 2048,
    hardware-irq-coalesce-rx-usecs => 1
  }
}

Where is ethtune's config file?
/etc/ethtune.conf

How does this compare to the ethtool module?

  * settings are lost during reboots
  * lost settings are only reapplied on the next puppet run
  * not all ethtool settings are supported

  ethtune solves the above.

How does this compare to the ethernet_tuning module?

  * all but 2 settings are lost during reboots
  * lost settings are only reapplied on the next puppet run

  ethtune solves the above.

How does this differ from managing ethtool settings via the interfaces files?

Functionally identical except ethtun supports bonding and teaming interfaces.
