linux-kernel - Re: [RFC v2 0/5] introduce gcma

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:	Tue, 24 Feb 2015 15:48:04 +0100
From:	Michal Hocko <mhocko@...e.cz>
To:	SeongJae Park <sj38.park@...il.com>
Cc:	akpm@...ux-foundation.org, lauraa@...eaurora.org,
	minchan@...nel.org, sergey.senozhatsky@...il.com,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 0/5] introduce gcma

On Tue 24-02-15 04:54:18, SeongJae Park wrote:
[...]
>  include/linux/cma.h  |    4 +
>  include/linux/gcma.h |   64 +++
>  mm/Kconfig           |   24 +
>  mm/Makefile          |    1 +
>  mm/cma.c             |  113 ++++-
>  mm/gcma.c            | 1321 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  6 files changed, 1508 insertions(+), 19 deletions(-)
>  create mode 100644 include/linux/gcma.h
>  create mode 100644 mm/gcma.c

Wow this is huge! And I do not see reason for it to be so big. Why
cannot you simply define (per-cma area) 2-class users policy? Either via
kernel command line or export areas to userspace and allow to set policy
there.

For starter something like the following policies should suffice AFAIU
your description.
	- NONE - exclusive pool for CMA allocations only
	- DROPABLE - only allocations which might be dropped without any
	  additional actions - e.g. cleancache and frontswap with
	  write-through policy
	- RECLAIMABLE - only movable allocations which can be migrated
	  or dropped after writeback.

Has such an approach been considered?
-- 
Michal Hocko
SUSE Labs
--
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/