On Tue, Sep 27, 2011 at 4:36 PM, Steve French <smfrench@xxxxxxxxx> wrote: > FYI - The cifs async write in 3.0 seems to exacerbate problems running > out of memory (apparently) on the Windows 7 system (running as a > server) after a large file copy to the server completes. I have been > able to reproduce the same problem on Windows Vista Service Pack 2 > (which is a good news/bad news story since my earlier testing on > Windows Vista showed hangs on some requests rather than returning out > of memory). Does not seem to be a problem with any of the Windows > server versions just Windows 7 and Vista so far If this is a problem with Windows Vista and Windows 7, it is likely to be a problem with Windows 2008 Server as well. Basically Windows server starting Vista perhaps? > > As Pavel noted in an earlier note, increasing MaxWorkItems to 4096 in > the Windows registry solves this. > > The cifs async write code does increase large file copy speed > dramatically (more than 15% in most environments) - but we are working > through how to handle the Windows7/WindowsVista problem to see if > there are workarounds. > > -- > Thanks, > > Steve > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
