From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2016, #07; Mon, 25)
Date: Wed, 27 Apr 2016 09:29:59 -0700 [thread overview]
Message-ID: <xmqqmvof9fqw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1604271454250.2896@virtualbox> (Johannes Schindelin's message of "Wed, 27 Apr 2016 14:56:27 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Mon, 25 Apr 2016, Junio C Hamano wrote:
>
>> * js/win32-mmap (2016-04-22) 3 commits
>> (merged to 'next' on 2016-04-22 at cd39c60)
>> + mmap(win32): avoid expensive fstat() call
>> + mmap(win32): avoid copy-on-write when it is unnecessary
>> + win32mmap: set errno appropriately
>>
>> mmap emulation on Windows has been optimized.
>
> Please note that it is not purely an optimization. It is also a bug fix in
> case of a pretty full disk: on Windows, mmap() is backed by the page file
> if it is in copy-on-write mode, and that can fail when the free space on
> the drive that has the page file drops below a certain threshold.
Thanks. How does this look then?
* js/win32-mmap (2016-04-22) 3 commits
(merged to 'next' on 2016-04-22 at cd39c60)
+ mmap(win32): avoid expensive fstat() call
+ mmap(win32): avoid copy-on-write when it is unnecessary
+ win32mmap: set errno appropriately
mmap emulation on Windows has been optimized and work better without
consuming paging store when not needed.
Will merge to 'master'.
Reducing paging file consumption still falls into optimization in my
dictionary, though ;-)
next prev parent reply other threads:[~2016-04-27 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 22:43 What's cooking in git.git (Apr 2016, #07; Mon, 25) Junio C Hamano
2016-04-27 12:56 ` Johannes Schindelin
2016-04-27 16:29 ` Junio C Hamano [this message]
2016-04-28 7:58 ` Johannes Schindelin
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=xmqqmvof9fqw.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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