public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: MinChan Kim <minchan.kim@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Lee Schermerhorn <lee.schermerhorn@hp.com>,
	Kosaki Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [patch 04/14] free swap space on swap-in/activation
Date: Mon, 19 May 2008 21:35:38 +0900	[thread overview]
Message-ID: <4831741A.7090206@gmail.com> (raw)
In-Reply-To: <20080516183224.259161900@redhat.com>

Hi, Rik.

I don't know where to send this patch. you or mm ?
I guess VM pageout patches didn't send mm-commits yet.

It made compile error in my system that didn't have swap device. 

----

Subject: [PATCH] Fix compile error about remove_exclusive_swap_page_ref

It happened compiled error when I removed CONFIG_SWAP in config file
It caused by new API that is 'remove_exclusive_swap_page_ref'.

Signed-off-by: MinChan Kim <minchan.kim@gmail.com>
---
 include/linux/swap.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/include/linux/swap.h b/include/linux/swap.h
index 4c3a2ef..f34fdb6 100644
--- a/include/linux/swap.h
+++ b/include/linux/swap.h
@@ -390,6 +390,11 @@ static inline int remove_exclusive_swap_page(struct page *p)
 	return 0;
 }
 
+static inline int remove_exclusive_swap_page_ref(struct page *page)
+{
+	return 0;
+}
+
 static inline swp_entry_t get_swap_page(void)
 {
 	swp_entry_t entry;
-- 
1.5.4.3

  reply	other threads:[~2008-05-19 12:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 18:32 [patch 00/14] VM pageout scalability improvements (V7) Rik van Riel
2008-05-16 18:32 ` [patch 01/14] move isolate_lru_page() to vmscan.c Rik van Riel
2008-05-16 18:32 ` [patch 02/14] Use an indexed array for LRU variables Rik van Riel
2008-05-16 18:32 ` [patch 03/14] use an array for the LRU pagevecs Rik van Riel
2008-05-16 18:32 ` [patch 04/14] free swap space on swap-in/activation Rik van Riel
2008-05-19 12:35   ` MinChan Kim [this message]
2008-05-19 16:01     ` Rik van Riel
2008-05-16 18:32 ` [patch 05/14] define page_file_cache() function Rik van Riel
2008-05-16 18:32 ` [patch 06/14] split LRU lists into anon & file sets Rik van Riel
2008-05-16 18:32 ` [patch 07/14] second chance replacement for anonymous pages Rik van Riel
2008-05-16 18:32 ` [patch 08/14] add some sanity checks to get_scan_ratio Rik van Riel
2008-05-16 18:32 ` [patch 09/14] add newly swapped in pages to the inactive list Rik van Riel
2008-05-16 18:32 ` [patch 10/14] more aggressively use lumpy reclaim Rik van Riel
2008-05-16 18:32 ` [patch 11/14] No Reclaim LRU Infrastructure Rik van Riel
2008-05-16 18:32 ` [patch 12/14] Non-reclaimable page statistics Rik van Riel
2008-05-16 18:32 ` [patch 13/14] ramfs pages are non-reclaimable Rik van Riel
2008-05-16 18:32 ` [patch 14/14] SHM_LOCKED pages are nonreclaimable Rik van Riel
2008-05-17  5:51 ` [patch 00/14] VM pageout scalability improvements (V7) MinChan Kim
2008-05-17 13:35   ` Rik van Riel

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=4831741A.7090206@gmail.com \
    --to=minchan.kim@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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