linux-kernel - Re: [RFC PATCH v2 2/2] mm: tuning hardcoded reserved memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Feb 2013 14:14:41 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andrew Shewmaker <agshew@...il.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 2/2] mm: tuning hardcoded reserved memory

On Wed, 27 Feb 2013 16:09:25 -0500
Andrew Shewmaker <agshew@...il.com> wrote:

> Add a rootuser_reserve_pages knob to allow admins of large memory 
> systems running with overcommit disabled to change the hardcoded 
> memory reserve to something other than 3%.
> 
> Signed-off-by: Andrew Shewmaker <agshew@...il.com>
> 
> ---
> 
> Patch based off of mmotm git tree as of February 27th.
> 
> I set rootuser_reserve pages to be a default of 1000, and I suppose 
> I should have initialzed similarly to the way min_free_kbytes is, 
> scaling it with the size of the box. However, I wanted to get a 
> simple version of this patch out for feedback to see if it has any 
> chance of acceptance or if I need to take an entirely different 
> approach.
> 
> Any feedback will be appreciated!

Seems reasonable.

Yes, we should scale the initial value according to the machine size in
some fashion.

btw, both these patches had the same title.  Please avoid this.
Documentation/SubmittingPatches section 15 has all the details.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/