On Wed, 28 Sep 2011 13:28:38 -0500 Steve French <[email protected]> wrote:
> On Wed, Sep 28, 2011 at 4:30 AM, Shirish Pargaonkar > <[email protected]> wrote: > > On Tue, Sep 27, 2011 at 4:36 PM, Steve French <[email protected]> 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? > > I have not been able to reproduce it against Windows 2003 > or Windows 2008 server yet, but plan some experiments. > If you have additional test data on this let me know. > > Most likely, those servers report a MaxMpx >= 50. The only real question I have is what maxmpx vista and 7 report. If it's <50 then this is likely our bug, not theirs. It seems quite correct for the server to return an error if the client exceeds that limit. -- Jeff Layton <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
