From: Paul Jackson <pj@sgi.com>
To: akpm@osdl.org, linux-kernel@vger.kernel.org
Cc: Simon Derr <Simon.Derr@bull.net>, Jack Steiner <steiner@sgi.com>,
Paul Jackson <pj@sgi.com>
Subject: [PATCH] cpuset export symbols gpl
Date: Tue, 15 Nov 2005 17:22:54 -0800 (PST) [thread overview]
Message-ID: <20051116012254.6470.89326.sendpatchset@jackhammer.engr.sgi.com> (raw)
Export the more useful cpuset routines for use by gpl modules.
Signed-off-by: Paul Jackson <pj@sgi.com>
---
kernel/cpuset.c | 5 +++++
1 files changed, 5 insertions(+)
--- 2.6.14-mm2.orig/kernel/cpuset.c 2005-11-15 16:05:12.717155260 -0800
+++ 2.6.14-mm2/kernel/cpuset.c 2005-11-15 16:14:25.425450732 -0800
@@ -1945,6 +1945,7 @@ cpumask_t cpuset_cpus_allowed(const stru
return mask;
}
+EXPORT_SYMBOL_GPL(cpuset_cpus_allowed);
void cpuset_init_current_mems_allowed(void)
{
@@ -1980,6 +1981,7 @@ done:
if (need_to_refresh)
refresh_mems();
}
+EXPORT_SYMBOL_GPL(cpuset_update_current_mems_allowed);
/**
* cpuset_zonelist_valid_mems_allowed - check zonelist vs. curremt mems_allowed
@@ -1999,6 +2001,7 @@ int cpuset_zonelist_valid_mems_allowed(s
}
return 0;
}
+EXPORT_SYMBOL_GPL(cpuset_zonelist_valid_mems_allowed);
/*
* nearest_exclusive_ancestor() - Returns the nearest mem_exclusive
@@ -2079,6 +2082,7 @@ int cpuset_zone_allowed(struct zone *z,
up(&callback_sem);
return allowed;
}
+EXPORT_SYMBOL_GPL(cpuset_zone_allowed);
/**
* cpuset_excl_nodes_overlap - Do we overlap @p's mem_exclusive ancestors?
@@ -2121,6 +2125,7 @@ done:
return overlap;
}
+EXPORT_SYMBOL_GPL(cpuset_excl_nodes_overlap);
/*
* Collection of memory_pressure is suppressed unless
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next reply other threads:[~2005-11-16 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 1:22 Paul Jackson [this message]
2005-11-16 1:39 ` [PATCH] cpuset export symbols gpl Andrew Morton
2005-11-16 2:03 ` Paul Jackson
2005-11-16 8:16 ` Christoph Hellwig
2005-11-16 14:33 ` Robin Holt
2005-11-17 1:04 ` Paul Jackson
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=20051116012254.6470.89326.sendpatchset@jackhammer.engr.sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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).