Skip to content
Snippets Groups Projects
  1. Jul 25, 2005
  2. Jul 22, 2005
  3. Jul 19, 2005
  4. Jul 12, 2005
    • Sam Ravnborg's avatar
      [NET]: move config options out to individual protocols · 6a2e9b73
      Sam Ravnborg authored
      
      Move the protocol specific config options out to the specific protocols.
      With this change net/Kconfig now starts to become readable and serve as a
      good basis for further re-structuring.
      
      The menu structure is left almost intact, except that indention is
      fixed in most cases. Most visible are the INET changes where several
      "depends on INET" are replaced with a single ifdef INET / endif pair.
      
      Several new files were created to accomplish this change - they are
      small but serve the purpose that config options are now distributed
      out where they belongs.
      
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      6a2e9b73
  5. Jul 09, 2005
  6. Jul 06, 2005
    • David S. Miller's avatar
      [TCP]: Move to new TSO segmenting scheme. · c1b4a7e6
      David S. Miller authored
      
      Make TSO segment transmit size decisions at send time not earlier.
      
      The basic scheme is that we try to build as large a TSO frame as
      possible when pulling in the user data, but the size of the TSO frame
      output to the card is determined at transmit time.
      
      This is guided by tp->xmit_size_goal.  It is always set to a multiple
      of MSS and tells sendmsg/sendpage how large an SKB to try and build.
      
      Later, tcp_write_xmit() and tcp_push_one() chop up the packet if
      necessary and conditions warrant.  These routines can also decide to
      "defer" in order to wait for more ACKs to arrive and thus allow larger
      TSO frames to be emitted.
      
      A general observation is that TSO elongates the pipe, thus requiring a
      larger congestion window and larger buffering especially at the sender
      side.  Therefore, it is important that applications 1) get a large
      enough socket send buffer (this is accomplished by our dynamic send
      buffer expansion code) 2) do large enough writes.
      
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c1b4a7e6
  7. Jul 05, 2005
  8. Jun 29, 2005
  9. Jun 28, 2005
  10. Jun 24, 2005
  11. Jun 23, 2005
  12. Jun 21, 2005
  13. Jun 20, 2005
  14. Jun 19, 2005
  15. Jun 14, 2005
    • Rémi Denis-Courmont's avatar
      [IPv6] Don't generate temporary for TUN devices · 77bd9196
      Rémi Denis-Courmont authored
      
      Userland layer-2 tunneling devices allocated through the TUNTAP driver 
      (drivers/net/tun.c) have a type of ARPHRD_NONE, and have no link-layer 
      address. The kernel complains at regular interval when IPv6 Privacy 
      extension are enabled because it can't find an hardware address :
      
      Dec 29 11:02:04 auguste kernel: __ipv6_regen_rndid(idev=cb3e0c00): 
      cannot get EUI64 identifier; use random bytes.
      
      IPv6 Privacy extensions should probably be disabled on that sort of 
      device. They won't work anyway. If userland wants a more usual 
      Ethernet-ish interface with usual IPv6 autoconfiguration, it will use a 
      TAP device with an emulated link-layer  and a random hardware address 
      rather than a TUN device.
      
      As far as I could fine, TUN virtual device from TUNTAP is the very only 
      sort of device using ARPHRD_NONE as kernel device type.
      
      Signed-off-by: default avatarRmi Denis-Courmont <rdenis@simphalempin.com>
      Acked-by: default avatarYOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      77bd9196
  16. Jun 13, 2005
  17. Jun 08, 2005
  18. Jun 02, 2005
  19. May 30, 2005
  20. May 26, 2005
Loading