From: Dmitry Potapov <dpotapov@gmail.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Chad Warner <chad.warner@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
msysgit@googlegroups.com, Johannes Sixt <j6t@kdbg.org>,
Sebastian Schuberth <sschuberth@gmail.com>,
dvornik+git@gmail.com
Subject: Re: [PATCH] Fix checkout of large files to network shares under Windows XP
Date: Sun, 17 Oct 2010 14:54:40 +0400 [thread overview]
Message-ID: <AANLkTinpwpckOn3BEHWn=4Tq_kRyOYYmYF5UQQ0qSpmS@mail.gmail.com> (raw)
In-Reply-To: <4CB9DF7E.1020203@lsrfire.ath.cx>
On Sat, Oct 16, 2010 at 9:23 PM, René Scharfe
<rene.scharfe@lsrfire.ath.cx> wrote:
>
> Also, 27KB is an odd number. I take it that 28KB won't fix the issue
> for you?
I guess the beginning of the written buffer is not page aligned, and the
system locks pages. Thus depending on the buffer alignment, the written
maximum can vary up to the size of one page.
>
> I wonder about the cause of this threshold. Wild guess: network driver
> bug or other network issue?
Memory pressure? Git may consume large amount of virtual memory
during some operations, but I am not sure how it is translated in the
number of physical memory consumed by the process as well as what
quotas could be on that system. It would be interesting to see what
GetProcessMemoryInfo() returns when write() fails.
Dmitry
prev parent reply other threads:[~2010-10-17 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 12:45 [PATCH] Fix checkout of large files to network shares under Windows XP Sebastian Schuberth
2010-04-19 20:41 ` Junio C Hamano
2010-04-20 9:15 ` Johannes Schindelin
2010-04-19 20:43 ` René Scharfe
2010-04-19 22:46 ` Albert Dvornik
2010-04-20 8:18 ` Johannes Sixt
2010-04-20 12:42 ` Sebastian Schuberth
2010-04-20 12:57 ` Johannes Sixt
2010-04-20 14:21 ` Sebastian Schuberth
2010-04-20 20:49 ` René Scharfe
2010-04-29 20:01 ` René Scharfe
2010-04-30 8:46 ` Johannes Sixt
2010-04-30 9:08 ` Sebastian Schuberth
[not found] ` <290b11b5-5dd5-4b83-a6f5-217797ebd5af@t8g2000yqk.googlegroups.com>
2010-10-16 17:23 ` René Scharfe
2010-10-17 10:54 ` Dmitry Potapov [this message]
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='AANLkTinpwpckOn3BEHWn=4Tq_kRyOYYmYF5UQQ0qSpmS@mail.gmail.com' \
--to=dpotapov@gmail.com \
--cc=chad.warner@gmail.com \
--cc=dvornik+git@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=msysgit@googlegroups.com \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=sschuberth@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).