On Aug 22, 2014, at 6:31 PM, Junio C Hamano wrote:
> Steffen Prohaska writes:
>
+ if (limit == -1) {
+ const char *env = getenv("GIT_MMAP_LIMIT");
+ limit = env ? atoi(env) * 1024 : 0;
>>
>> ... this should then be changed to atol(env), and ...
>
> In the re
Junio C Hamano writes:
> Steffen Prohaska writes:
>
+ if (limit == -1) {
+ const char *env = getenv("GIT_MMAP_LIMIT");
+ limit = env ? atoi(env) * 1024 : 0;
>>
>> ... this should then be changed to atol(env), and ...
>
> In the real codepath (not debugging aid
Steffen Prohaska writes:
>>> + if (limit == -1) {
>>> + const char *env = getenv("GIT_MMAP_LIMIT");
>>> + limit = env ? atoi(env) * 1024 : 0;
>
> ... this should then be changed to atol(env), and ...
In the real codepath (not debugging aid like this) we try to avoid
atoi/a
On Aug 22, 2014, at 12:26 AM, Junio C Hamano wrote:
> Steffen Prohaska writes:
>
>> Similar to testing expectations about malloc with GIT_ALLOC_LIMIT (see
>> commit d41489), it can be useful to test expectations about mmap.
>>
>> This introduces a new environment variable GIT_MMAP_LIMIT to li
Steffen Prohaska writes:
> Similar to testing expectations about malloc with GIT_ALLOC_LIMIT (see
> commit d41489), it can be useful to test expectations about mmap.
>
> This introduces a new environment variable GIT_MMAP_LIMIT to limit the
> largest allowed mmap length (in KB). xmmap() is modif
Similar to testing expectations about malloc with GIT_ALLOC_LIMIT (see
commit d41489), it can be useful to test expectations about mmap.
This introduces a new environment variable GIT_MMAP_LIMIT to limit the
largest allowed mmap length (in KB). xmmap() is modified to check the
limit. Together wi
6 matches
Mail list logo