From: Michal Hocko <mhocko@suse.cz>
To: SeongJae Park <sj38.park@gmail.com>
Cc: akpm@linux-foundation.org, lauraa@codeaurora.org,
minchan@kernel.org, sergey.senozhatsky@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 0/5] introduce gcma
Date: Tue, 24 Feb 2015 15:48:04 +0100 [thread overview]
Message-ID: <20150224144804.GE15626@dhcp22.suse.cz> (raw)
In-Reply-To: <1424721263-25314-1-git-send-email-sj38.park@gmail.com>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-24 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 19:54 SeongJae Park
2015-02-23 19:54 ` [RFC v2 1/5] gcma: introduce contiguous memory allocator SeongJae Park
2015-02-23 19:54 ` [RFC v2 2/5] gcma: utilize reserved memory as discardable memory SeongJae Park
2015-02-23 19:54 ` [RFC v2 3/5] gcma: adopt cleancache and frontswap as second-class clients SeongJae Park
2015-02-23 19:54 ` [RFC v2 4/5] gcma: export statistical data on debugfs SeongJae Park
2015-02-23 19:54 ` [RFC v2 5/5] gcma: integrate gcma under cma interface SeongJae Park
2015-02-24 14:48 ` Michal Hocko [this message]
2015-02-25 5:31 ` [RFC v2 0/5] introduce gcma SeongJae Park
2015-02-25 16:11 ` Michal Hocko
2015-02-25 16:47 ` SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150224144804.GE15626@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sj38.park@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox