Re: [PATCH] Expand on impact of threads on memory consumption.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robert de Bath <rdebath@xxxxxxxxxxxxxxxxx> writes:

> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index c55c22a..6384038 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1828,7 +1828,10 @@ pack.depth::
>  
>  pack.windowMemory::
>  	The window memory size limit used by linkgit:git-pack-objects[1]
> -	when no limit is given on the command line.  The value can be
> +	when no limit is given on the command line.  This limit may be
> +	allocated individually by each thread doing delta compression
> +	so the total memory allocated by linkgit:git-pack-objects[1] can
> +	be this multiplied by the number of threads.  The value can be
>  	suffixed with "k", "m", or "g".  Defaults to 0, meaning no
>  	limit.

I sense that this change makes the resulting text unnecessarily
opaque by avoiding touching the first sentence.  Wouldn't something
more concise like this sufficient?

    The default maximum size of memory that is consumed by each
    thread in linkgit:git-pack-objects[1] for pack window memory.
    The value can be suffixed with "k", "m", or "g".  When left
    unconfigured, there will be no limit.



--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]