- Original Message -
> From: "Dave Hansen"
> To: "Andrew Morton" , "Jerome Marchand"
>
> Cc: linux...@kvack.org, linux-kernel@vger.kernel.org
> Sent: Thursday, November 7, 2013 12:49:54 AM
> Subject: Re: [PATCH v4 2/2] mm: allow to s
On 11/06/2013 02:33 PM, Andrew Morton wrote:
> On Wed, 6 Nov 2013 03:42:20 -0500 (EST) Jerome Marchand
> wrote:
>> That was my first version of this patch (actually "kbytes" to avoid
>> overflow).
>> Dave raised the issue that it silently breaks the user interface:
>> overcommit_ratio is zero whi
> > Sent: Wednesday, November 6, 2013 12:53:19 AM
> > Subject: Re: [PATCH v4 2/2] mm: allow to set overcommit ratio more precisely
> >
> > On Fri, 18 Oct 2013 14:56:59 +0200 Jerome Marchand
> > wrote:
> >
> > > Some applications that run on HPC
- Original Message -
> From: "Andrew Morton"
> To: "Jerome Marchand"
> Cc: linux...@kvack.org, linux-kernel@vger.kernel.org, "dave hansen"
>
> Sent: Wednesday, November 6, 2013 12:53:19 AM
> Subject: Re: [PATCH v4 2/2] mm: allow to set
On Fri, 18 Oct 2013 14:56:59 +0200 Jerome Marchand wrote:
> Some applications that run on HPC clusters are designed around the
> availability of RAM and the overcommit ratio is fine tuned to get the
> maximum usage of memory without swapping. With growing memory, the 1%
> of all RAM grain provide
Changes since v3:
- rebase on 3.12-rc5
Changes since v2:
- updates documentation
Changes since v1:
- use overcommit_ratio_ppm instead of overcommit_kbytes
- keep both variables in sync
Some applications that run on HPC clusters are designed around the
availability of RAM and the overcommit rat
6 matches
Mail list logo