1. 20 Apr, 2009 3 commits
  2. 31 Mar, 2009 3 commits
  3. 30 Mar, 2009 11 commits
  4. 27 Mar, 2009 1 commit
  5. 26 Mar, 2009 4 commits
  6. 25 Mar, 2009 1 commit
  7. 24 Mar, 2009 2 commits
  8. 22 Mar, 2009 2 commits
    • set mtu for netdev · 75d09f83
      Daniel Lezcano authored
      When setting the mtu size at the veth creation, the mtu is only set
      on one side of the veth tunnel, the one attached to the bridge.
      
      I changed a little the code and added the device_set_mtu function so
      it is called after the veth has been created on both side.
      
      That moves the mtu veth specific code inside the veth function creation.
      
      Hopefully this code could be reused later for different future network
      configuration (eg. ip tunnel).
      
      The mtu option will be simply ignored in case of macvlan network configuration
      because the macvlan network device inherit the mtu of the physical link.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • Add lxc.network.mtu configuration (resend) · 442cbbe6
      Takano Ryousei authored
      Hi Daniel,
      
      I resent my patch. I hope to fix folding failure.
      
      This patch allows users to specify the MTU size of the veth interface.
       It helps to use jumbo frames on the container.
      
      Changes from v1:
      	- Fix failing if the 'mtu' is not specified.
      	- Delete the 'mtu' entry at time of lxc-destroy.
      Signed-off-by: 's avatarRyousei Takano <takano-ryousei@aist.go.jp>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  9. 20 Mar, 2009 2 commits
  10. 19 Mar, 2009 5 commits
  11. 16 Mar, 2009 1 commit
  12. 11 Mar, 2009 1 commit
  13. 10 Mar, 2009 1 commit
  14. 09 Mar, 2009 2 commits
  15. 08 Mar, 2009 1 commit
    • define signalfd patch · 8ca61733
      Michael K. Johnson authored
      If sys/signalfd.h does not exist, assume that it does not exist
      in glibc, rather than that it exists without a corresponding
      header file.  Note that this version of the signalfd() wrapper
      function (unlike the version in glibc) falls back dynamically to
      the old signalfd system call if the signalfd4 system call is not
      implemented in the currently-running kernel; the version in glibc
      chooses the version of the signalfd system call to make via static
      build-time configuration.
      Signed-off-by: 's avatarMichael K Johnson <johnsonm@rpath.com>
      Signed-off-by: 's avatarDaniel Lezcnao <dlezcano@fr.ibm.com>