1. 12 9月, 2009 1 次提交
  2. 25 8月, 2009 1 次提交
  3. 15 7月, 2009 1 次提交
  4. 19 6月, 2009 1 次提交
    • T
      SUNRPC: Fix the TCP server's send buffer accounting · 47fcb03f
      Trond Myklebust 提交于
      Currently, the sunrpc server is refusing to allow us to process new RPC
      calls if the TCP send buffer is 2/3 full, even if we do actually have
      enough free space to guarantee that we can send another request.
      The following patch fixes svc_tcp_has_wspace() so that we only stop
      processing requests if we know that the socket buffer cannot possibly fit
      another reply.
      
      It also fixes the tcp write_space() callback so that we only clear the
      SOCK_NOSPACE flag when the TCP send buffer is less than 2/3 full.
      This should ensure that the send window will grow as per the standard TCP
      socket code.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      47fcb03f
  5. 18 6月, 2009 1 次提交
  6. 28 5月, 2009 1 次提交
  7. 29 4月, 2009 6 次提交
  8. 02 4月, 2009 1 次提交
  9. 29 3月, 2009 3 次提交
  10. 19 3月, 2009 1 次提交
    • O
      svcrpc: take advantage of tcp autotuning · 47a14ef1
      Olga Kornievskaia 提交于
      Allow the NFSv4 server to make use of TCP autotuning behaviour, which
      was previously disabled by setting the sk_userlocks variable.
      
      Set the receive buffers to be big enough to receive the whole RPC
      request, and set this for the listening socket, not the accept socket.
      
      Remove the code that readjusts the receive/send buffer sizes for the
      accepted socket. Previously this code was used to influence the TCP
      window management behaviour, which is no longer needed when autotuning
      is enabled.
      
      This can improve IO bandwidth on networks with high bandwidth-delay
      products, where a large tcp window is required.  It also simplifies
      performance tuning, since getting adequate tcp buffers previously
      required increasing the number of nfsd threads.
      Signed-off-by: NOlga Kornievskaia <aglo@citi.umich.edu>
      Cc: Jim Rees <rees@umich.edu>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      47a14ef1
  11. 08 1月, 2009 2 次提交
  12. 07 1月, 2009 1 次提交
  13. 25 11月, 2008 1 次提交
  14. 31 10月, 2008 1 次提交
  15. 05 10月, 2008 1 次提交
  16. 30 9月, 2008 1 次提交
    • C
      SUNRPC: Set V6ONLY socket option for RPC listener sockets · b6632339
      Chuck Lever 提交于
      My plan is to use an AF_INET listener on systems that support only IPv4,
      and an AF_INET6 listener on systems that can support IPv6. Incoming
      IPv4 packets will be posted to an AF_INET6 listener with a mapped IPv4
      address.
      
      Max Matveev <makc@sgi.com> says:
        Creating a single listener can be dangerous - if net.ipv6.bindv6only
        is enabled then it's possible to create another listener in v4
        namespace on the same port and steal the traffic from the "unifed"
        listener. You need to disable V6ONLY explicitly via a sockopt to stop
        that.
      
      Set appropriate socket option on RPC server listener sockets to prevent
      this.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      b6632339
  17. 24 4月, 2008 3 次提交
  18. 22 2月, 2008 1 次提交
  19. 02 2月, 2008 12 次提交