1. 07 1月, 2006 4 次提交
    • C
      NFS: support large reads and writes on the wire · 40859d7e
      Chuck Lever 提交于
       Most NFS server implementations allow up to 64KB reads and writes on the
       wire.  The Solaris NFS server allows up to a megabyte, for instance.
      
       Now the Linux NFS client supports transfer sizes up to 1MB, too.  This will
       help reduce protocol and context switch overhead on read/write intensive NFS
       workloads, and support larger atomic read and write operations on servers
       that support them.
      
       Test-plan:
       Connectathon and iozone on mount point with wsize=rsize>32768 over TCP.
       Tests with NFS over UDP to verify the maximum RPC payload size cap.
      Signed-off-by: NChuck Lever <cel@netapp.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      40859d7e
    • C
      NFS: use generic_write_checks() to sanity check direct writes · ce1a8e67
      Chuck Lever 提交于
       Replace ad hoc write parameter sanity checking in nfs_file_direct_write()
       with a call to generic_write_checks().  This should make the proper checks
       modulo the O_LARGEFILE flag, and should catch NFSv2-specific limitations by
       virtue of i_sb->s_maxbytes.
      
       Test plan:
       Posix compliance testing with both NFSv2 and NFSv3.
      Signed-off-by: NChuck Lever <cel@netapp.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      ce1a8e67
    • T
      NFSv4: stateful NFSv4 RPC call interface · 44c28873
      Trond Myklebust 提交于
       The NFSv4 model requires us to complete all RPC calls that might
       establish state on the server whether or not the user wants to
       interrupt it. We may also need to schedule new work (including
       new RPC calls) in order to cancel the new state.
      
       The asynchronous RPC model will allow us to ensure that RPC calls
       always complete, but in order to allow for "synchronous" RPC, we
       want to add the ability to wait for completion.
       The waits are, of course, interruptible.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      44c28873
    • T
      RPC: Clean up RPC task structure · 963d8fe5
      Trond Myklebust 提交于
       Shrink the RPC task structure. Instead of storing separate pointers
       for task->tk_exit and task->tk_release, put them in a structure.
      
       Also pass the user data pointer as a parameter instead of passing it via
       task->tk_calldata. This enables us to nest callbacks.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      963d8fe5
  2. 20 12月, 2005 1 次提交
  3. 05 11月, 2005 1 次提交
  4. 24 6月, 2005 1 次提交
  5. 23 6月, 2005 1 次提交
    • T
      [PATCH] NFS: Fix the file size revalidation · 951a143b
      Trond Myklebust 提交于
       Instead of looking at whether or not the file is open for writes before
       we accept to update the length using the server value, we should rather
       be looking at whether or not we are currently caching any writes.
      
       Failure to do so means in particular that we're not updating the file
       length correctly after obtaining a POSIX or BSD lock.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      951a143b
  6. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4