1. 15 3月, 2008 1 次提交
    • S
      [CIFS] file create with acl support enabled is slow · 8b1327f6
      Steve French 提交于
      Shirish Pargaonkar noted:
      With cifsacl mount option, when a file is created on the Windows server,
      exclusive oplock is broken right away because the get cifs acl code
      again opens the file to obtain security descriptor.
      The client does not have the newly created file handle or inode in any
      of its lists yet so it does not respond to oplock break and server waits for
      its duration and then responds to the second open. This slows down file
      creation signficantly.  The fix is to pass the file descriptor to the get
      cifsacl code wherever available so that get cifs acl code does not send
      second open (NT Create ANDX) and oplock is not broken.
      
      CC: Shirish Pargaonkar <shirishp@us.ibm.com>
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      8b1327f6
  2. 13 2月, 2008 2 次提交
  3. 08 2月, 2008 1 次提交
  4. 31 12月, 2007 1 次提交
  5. 06 12月, 2007 1 次提交
  6. 25 11月, 2007 1 次提交
  7. 09 11月, 2007 2 次提交
  8. 06 11月, 2007 1 次提交
  9. 02 11月, 2007 1 次提交
  10. 31 10月, 2007 1 次提交
  11. 30 10月, 2007 1 次提交
  12. 27 10月, 2007 1 次提交
  13. 26 10月, 2007 2 次提交
  14. 24 10月, 2007 1 次提交
  15. 20 10月, 2007 1 次提交
  16. 18 10月, 2007 2 次提交
  17. 17 10月, 2007 4 次提交
  18. 13 10月, 2007 1 次提交
  19. 12 10月, 2007 1 次提交
  20. 04 10月, 2007 2 次提交
  21. 02 10月, 2007 1 次提交
  22. 26 9月, 2007 2 次提交