From: Christoph Lameter <clameter@engr.sgi.com>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-git9 build failure when CONFIG_SWAP is not set
Date: Fri, 13 Jan 2006 16:49:17 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0601131648320.7664@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060113223108.GA3709@localhost.localdomain>
On Fri, 13 Jan 2006, Ravikiran G Thirumalai wrote:
> Compile fails when CONFIG_SWAP is not set. Attaching the .config for
> reference.
-- Patch that was sent to Andrew.
Some people apparently run CONFIG_NUMA without CONFIG_SWAP. The migration
code currently depends on swap. This patch provides a set of inline fallback
functions so that the kernel properly compiles. Howeverver, calls to migration
functions will fail.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.15/include/linux/swap.h
===================================================================
--- linux-2.6.15.orig/include/linux/swap.h 2006-01-11 12:49:03.000000000 -0800
+++ linux-2.6.15/include/linux/swap.h 2006-01-13 16:41:19.000000000 -0800
@@ -180,6 +180,11 @@ extern int isolate_lru_page(struct page
extern int putback_lru_pages(struct list_head *l);
extern int migrate_pages(struct list_head *l, struct list_head *t,
struct list_head *moved, struct list_head *failed);
+#else
+static inline int isolate_lru_page(struct page *p) { return -ENOSYS; }
+static inline int putback_lru_pages(struct list_head *l) { return 0; }
+static inline int migrate_pages(struct list_head *l, struct list_head *t,
+ struct list_head *moved, struct list_head *failed) { return -ENOSYS; }
#endif
#ifdef CONFIG_MMU
prev parent reply other threads:[~2006-01-14 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 22:31 Ravikiran G Thirumalai
2006-01-14 0:11 ` yhlu
2006-01-14 0:49 ` Christoph Lameter [this message]
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=Pine.LNX.4.62.0601131648320.7664@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®