From: Ying Han <yinghan@google.com>
To: Nick Piggin <npiggin@kernel.dk>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Tejun Heo <tj@kernel.org>, Pavel Emelyanov <xemul@openvz.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>, Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <cl@linux.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
Michal Hocko <mhocko@suse.cz>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Zhu Yanhai <zhu.yanhai@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 1/3] move scan_control definition to header file
Date: Tue, 19 Apr 2011 10:58:32 -0700 [thread overview]
Message-ID: <BANLkTinoz_+DW40fV23j1-PeTbHHEXcywA@mail.gmail.com> (raw)
In-Reply-To: <1303235496-3060-2-git-send-email-yinghan@google.com>
[-- Attachment #1: Type: text/plain, Size: 5674 bytes --]
On Tue, Apr 19, 2011 at 10:51 AM, Ying Han <yinghan@google.com> wrote:
> This patch moves the scan_control definition from vmscan to swap.h
> header file, which is needed later to pass the struct to shrinkers.
>
> Signed-off-by: Ying Han <yinghan@google.com>
> ---
> include/linux/swap.h | 61
> ++++++++++++++++++++++++++++++++++++++++++++++++++
> mm/vmscan.c | 61
> --------------------------------------------------
> 2 files changed, 61 insertions(+), 61 deletions(-)
>
> diff --git a/include/linux/swap.h b/include/linux/swap.h
> index ed6ebe6..cb48fbd 100644
> --- a/include/linux/swap.h
> +++ b/include/linux/swap.h
> @@ -16,6 +16,67 @@ struct notifier_block;
>
> struct bio;
>
> +/*
> + * reclaim_mode determines how the inactive list is shrunk
> + * RECLAIM_MODE_SINGLE: Reclaim only order-0 pages
> + * RECLAIM_MODE_ASYNC: Do not block
> + * RECLAIM_MODE_SYNC: Allow blocking e.g. call wait_on_page_writeback
> + * RECLAIM_MODE_LUMPYRECLAIM: For high-order allocations, take a reference
> + * page from the LRU and reclaim all pages within a
> + * naturally aligned range
> + * RECLAIM_MODE_COMPACTION: For high-order allocations, reclaim a number
> of
> + * order-0 pages and then compact the zone
> + */
> +typedef unsigned __bitwise__ reclaim_mode_t;
> +#define RECLAIM_MODE_SINGLE ((__force reclaim_mode_t)0x01u)
> +#define RECLAIM_MODE_ASYNC ((__force reclaim_mode_t)0x02u)
> +#define RECLAIM_MODE_SYNC ((__force reclaim_mode_t)0x04u)
> +#define RECLAIM_MODE_LUMPYRECLAIM ((__force reclaim_mode_t)0x08u)
> +#define RECLAIM_MODE_COMPACTION ((__force
> reclaim_mode_t)0x10u)
> +
> +struct scan_control {
> + /* Incremented by the number of inactive pages that were scanned */
> + unsigned long nr_scanned;
> +
> + /* Number of pages freed so far during a call to shrink_zones() */
> + unsigned long nr_reclaimed;
> +
> + /* How many pages shrink_list() should reclaim */
> + unsigned long nr_to_reclaim;
> +
> + unsigned long hibernation_mode;
> +
> + /* This context's GFP mask */
> + gfp_t gfp_mask;
> +
> + int may_writepage;
> +
> + /* Can mapped pages be reclaimed? */
> + int may_unmap;
> +
> + /* Can pages be swapped as part of reclaim? */
> + int may_swap;
> +
> + int swappiness;
> +
> + int order;
> +
> + /*
> + * Intend to reclaim enough continuous memory rather than reclaim
> + * enough amount of memory. i.e, mode for high order allocation.
> + */
> + reclaim_mode_t reclaim_mode;
> +
> + /* Which cgroup do we reclaim from */
> + struct mem_cgroup *mem_cgroup;
> +
> + /*
> + * Nodemask of nodes allowed by the caller. If NULL, all nodes
> + * are scanned.
> + */
> + nodemask_t *nodemask;
> +};
> +
> #define SWAP_FLAG_PREFER 0x8000 /* set if swap priority specified
> */
> #define SWAP_FLAG_PRIO_MASK 0x7fff
> #define SWAP_FLAG_PRIO_SHIFT 0
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 060e4c1..08b1ab5 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -52,67 +52,6 @@
> #define CREATE_TRACE_POINTS
> #include <trace/events/vmscan.h>
>
> -/*
> - * reclaim_mode determines how the inactive list is shrunk
> - * RECLAIM_MODE_SINGLE: Reclaim only order-0 pages
> - * RECLAIM_MODE_ASYNC: Do not block
> - * RECLAIM_MODE_SYNC: Allow blocking e.g. call wait_on_page_writeback
> - * RECLAIM_MODE_LUMPYRECLAIM: For high-order allocations, take a reference
> - * page from the LRU and reclaim all pages within a
> - * naturally aligned range
> - * RECLAIM_MODE_COMPACTION: For high-order allocations, reclaim a number
> of
> - * order-0 pages and then compact the zone
> - */
> -typedef unsigned __bitwise__ reclaim_mode_t;
> -#define RECLAIM_MODE_SINGLE ((__force reclaim_mode_t)0x01u)
> -#define RECLAIM_MODE_ASYNC ((__force reclaim_mode_t)0x02u)
> -#define RECLAIM_MODE_SYNC ((__force reclaim_mode_t)0x04u)
> -#define RECLAIM_MODE_LUMPYRECLAIM ((__force reclaim_mode_t)0x08u)
> -#define RECLAIM_MODE_COMPACTION ((__force
> reclaim_mode_t)0x10u)
> -
> -struct scan_control {
> - /* Incremented by the number of inactive pages that were scanned */
> - unsigned long nr_scanned;
> -
> - /* Number of pages freed so far during a call to shrink_zones() */
> - unsigned long nr_reclaimed;
> -
> - /* How many pages shrink_list() should reclaim */
> - unsigned long nr_to_reclaim;
> -
> - unsigned long hibernation_mode;
> -
> - /* This context's GFP mask */
> - gfp_t gfp_mask;
> -
> - int may_writepage;
> -
> - /* Can mapped pages be reclaimed? */
> - int may_unmap;
> -
> - /* Can pages be swapped as part of reclaim? */
> - int may_swap;
> -
> - int swappiness;
> -
> - int order;
> -
> - /*
> - * Intend to reclaim enough continuous memory rather than reclaim
> - * enough amount of memory. i.e, mode for high order allocation.
> - */
> - reclaim_mode_t reclaim_mode;
> -
> - /* Which cgroup do we reclaim from */
> - struct mem_cgroup *mem_cgroup;
> -
> - /*
> - * Nodemask of nodes allowed by the caller. If NULL, all nodes
> - * are scanned.
> - */
> - nodemask_t *nodemask;
> -};
> -
> #define lru_to_page(_head) (list_entry((_head)->prev, struct page, lru))
>
> #ifdef ARCH_HAS_PREFETCH
> --
> 1.7.3.1
>
>
[-- Attachment #2: Type: text/html, Size: 6459 bytes --]
next prev parent reply other threads:[~2011-04-19 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 17:51 [PATCH 0/3] pass the scan_control into shrinkers Ying Han
2011-04-19 17:51 ` [PATCH 1/3] move scan_control definition to header file Ying Han
2011-04-19 17:58 ` Ying Han [this message]
2011-04-19 20:30 ` Rik van Riel
2011-04-19 17:51 ` [PATCH 2/3] change the shrink_slab by passing scan_control Ying Han
2011-04-19 18:02 ` Ying Han
2011-04-19 20:30 ` Rik van Riel
2011-04-19 17:51 ` [PATCH 3/3] change shrinker API by passing scan_control struct Ying Han
2011-04-19 18:03 ` Ying Han
2011-04-19 20:30 ` Rik van Riel
2011-04-19 17:55 ` [PATCH 0/3] pass the scan_control into shrinkers Ying Han
2011-04-20 0:20 ` KOSAKI Motohiro
2011-04-20 0:51 ` Ying Han
2011-04-20 0:54 ` KOSAKI Motohiro
2011-04-20 1:03 ` Ying Han
2011-04-20 1:25 ` KOSAKI Motohiro
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=BANLkTinoz_+DW40fV23j1-PeTbHHEXcywA@mail.gmail.com \
--to=yinghan@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=mel@csn.ul.ie \
--cc=mhocko@suse.cz \
--cc=minchan.kim@gmail.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=npiggin@kernel.dk \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=xemul@openvz.org \
--cc=zhu.yanhai@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;
as well as URLs for NNTP newsgroup(s).