From: Jeremy Allison <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
samba-technical
<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>
Subject: Re: Mounts to Windows 7 and "out of memory" or "insufficient server resources"
Date: Tue, 27 Sep 2011 16:01:55 -0700 [thread overview]
Message-ID: <20110927230155.GF23739@samba2> (raw)
In-Reply-To: <CAH2r5msivsE_47mESmGR=Xjf2v-kKwi-Qpym2kxuTLPbYudisQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Sep 27, 2011 at 04:36:22PM -0500, Steve French 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.
>
> 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.
Have you notified the Microsoft engineers about this ? I can
give you the right names to bug...
Jeremy.
next prev parent reply other threads:[~2011-09-27 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 21:36 Mounts to Windows 7 and "out of memory" or "insufficient server resources" Steve French
[not found] ` <CAH2r5msivsE_47mESmGR=Xjf2v-kKwi-Qpym2kxuTLPbYudisQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-27 23:01 ` Jeremy Allison [this message]
2011-09-27 23:18 ` Steve French
2011-09-28 5:47 ` Suresh Jayaraman
[not found] ` <4E82B4ED.4060107-IBi9RG/b67k@public.gmane.org>
2011-09-28 12:06 ` Jeff Layton
[not found] ` <20110928080622.5e30429b-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-09-28 18:27 ` Steve French
[not found] ` <CAH2r5msGRvhahCXbAb8mj7c28qUzPxOB5dJjjyQFAZvQxZzY-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-28 19:54 ` Jeff Layton
[not found] ` <20110928155404.12b84af3-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-09-29 5:12 ` Suresh Jayaraman
[not found] ` <4E83FE54.7060309-IBi9RG/b67k@public.gmane.org>
2011-09-29 10:47 ` Jeff Layton
2011-09-28 9:30 ` Shirish Pargaonkar
[not found] ` <CADT32eLk5N4WJCMdtcd3MTgR39fCTn4_gQqqobYsxkpcPnfuDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-28 18:28 ` Steve French
[not found] ` <CAH2r5msGzs65HO_YuuUzhp3RNo+rJEB=ey8Hx5=1r=bpWpjWLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-28 19:56 ` Jeff Layton
[not found] ` <20110928155648.09c19e8c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-09-29 1:22 ` Steve French
2011-09-28 12:00 ` Jeff Layton
[not found] ` <20110928080027.2c04b12d-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-09-28 18:25 ` Steve French
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110927230155.GF23739@samba2 \
--to=jra-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox