From: Dean Nelson <dcn@sgi.com>
To: akpm@linux-foundation.org
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, tony.luck@intel.com, jes@sgi.com
Subject: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 15:59:33 +0000 [thread overview]
Message-ID: <20070827155933.GB25589@sgi.com> (raw)
In-Reply-To: <20070827155622.GA25589@sgi.com>
This patch exports __put_task_struct as it is needed by XPMEM.
Signed-off-by: Dean Nelson <dcn@sgi.com>
---
One struct file_operations registered by XPMEM, xpmem_open(), calls
'get_task_struct(current->group_leader)' and another, xpmem_flush(), calls
'put_task_struct(tg->group_leader)'. The reason for this is given in the
comment block that appears in xpmem_open().
/*
* Increment 'usage' and 'mm->mm_users' for the current task's thread
* group leader. This ensures that both its task_struct and mm_struct
* will still be around when our thread group exits. (The Linux kernel
* normally tears down the mm_struct prior to calling a module's
* 'flush' function.) Since all XPMEM thread groups must go through
* this path, this extra reference to mm_users also allows us to
* directly inc/dec mm_users in xpmem_ensure_valid_PFNs() and avoid
* mmput() which has a scaling issue with the mmlist_lock.
*/
Index: linux-2.6/kernel/fork.c
=================================--- linux-2.6.orig/kernel/fork.c 2007-08-09 07:07:55.426611601 -0500
+++ linux-2.6/kernel/fork.c 2007-08-09 07:15:43.246391700 -0500
@@ -127,6 +127,7 @@
if (!profile_handoff_task(tsk))
free_task(tsk);
}
+EXPORT_SYMBOL_GPL(__put_task_struct);
void __init fork_init(unsigned long mempages)
{
WARNING: multiple messages have this Message-ID (diff)
From: Dean Nelson <dcn@sgi.com>
To: akpm@linux-foundation.org
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, tony.luck@intel.com, jes@sgi.com
Subject: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 10:59:33 -0500 [thread overview]
Message-ID: <20070827155933.GB25589@sgi.com> (raw)
In-Reply-To: <20070827155622.GA25589@sgi.com>
This patch exports __put_task_struct as it is needed by XPMEM.
Signed-off-by: Dean Nelson <dcn@sgi.com>
---
One struct file_operations registered by XPMEM, xpmem_open(), calls
'get_task_struct(current->group_leader)' and another, xpmem_flush(), calls
'put_task_struct(tg->group_leader)'. The reason for this is given in the
comment block that appears in xpmem_open().
/*
* Increment 'usage' and 'mm->mm_users' for the current task's thread
* group leader. This ensures that both its task_struct and mm_struct
* will still be around when our thread group exits. (The Linux kernel
* normally tears down the mm_struct prior to calling a module's
* 'flush' function.) Since all XPMEM thread groups must go through
* this path, this extra reference to mm_users also allows us to
* directly inc/dec mm_users in xpmem_ensure_valid_PFNs() and avoid
* mmput() which has a scaling issue with the mmlist_lock.
*/
Index: linux-2.6/kernel/fork.c
===================================================================
--- linux-2.6.orig/kernel/fork.c 2007-08-09 07:07:55.426611601 -0500
+++ linux-2.6/kernel/fork.c 2007-08-09 07:15:43.246391700 -0500
@@ -127,6 +127,7 @@
if (!profile_handoff_task(tsk))
free_task(tsk);
}
+EXPORT_SYMBOL_GPL(__put_task_struct);
void __init fork_init(unsigned long mempages)
{
WARNING: multiple messages have this Message-ID (diff)
From: Dean Nelson <dcn@sgi.com>
To: akpm@linux-foundation.org
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, tony.luck@intel.com, jes@sgi.com
Subject: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 10:59:33 -0500 [thread overview]
Message-ID: <20070827155933.GB25589@sgi.com> (raw)
In-Reply-To: <20070827155622.GA25589@sgi.com>
This patch exports __put_task_struct as it is needed by XPMEM.
Signed-off-by: Dean Nelson <dcn@sgi.com>
---
One struct file_operations registered by XPMEM, xpmem_open(), calls
'get_task_struct(current->group_leader)' and another, xpmem_flush(), calls
'put_task_struct(tg->group_leader)'. The reason for this is given in the
comment block that appears in xpmem_open().
/*
* Increment 'usage' and 'mm->mm_users' for the current task's thread
* group leader. This ensures that both its task_struct and mm_struct
* will still be around when our thread group exits. (The Linux kernel
* normally tears down the mm_struct prior to calling a module's
* 'flush' function.) Since all XPMEM thread groups must go through
* this path, this extra reference to mm_users also allows us to
* directly inc/dec mm_users in xpmem_ensure_valid_PFNs() and avoid
* mmput() which has a scaling issue with the mmlist_lock.
*/
Index: linux-2.6/kernel/fork.c
===================================================================
--- linux-2.6.orig/kernel/fork.c 2007-08-09 07:07:55.426611601 -0500
+++ linux-2.6/kernel/fork.c 2007-08-09 07:15:43.246391700 -0500
@@ -127,6 +127,7 @@
if (!profile_handoff_task(tsk))
free_task(tsk);
}
+EXPORT_SYMBOL_GPL(__put_task_struct);
void __init fork_init(unsigned long mempages)
{
--
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:[~2007-08-27 15:59 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 15:56 [PATCH 0/4] SGI Altix cross partition memory (XPMEM) Dean Nelson
2007-08-27 15:56 ` Dean Nelson
2007-08-27 15:56 ` Dean Nelson
2007-08-27 15:59 ` Dean Nelson [this message]
2007-08-27 15:59 ` [PATCH 1/4] export __put_task_struct for XPMEM Dean Nelson
2007-08-27 15:59 ` Dean Nelson
2007-08-27 16:13 ` Al Viro
2007-08-27 16:13 ` Al Viro
2007-08-27 16:13 ` Al Viro
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:15 ` Al Viro
2007-08-27 18:15 ` Al Viro
2007-08-27 18:15 ` Al Viro
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:35 ` Al Viro
2007-08-27 19:35 ` Al Viro
2007-08-27 19:35 ` Al Viro
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:47 ` Al Viro
2007-08-27 20:47 ` Al Viro
2007-08-27 20:47 ` Al Viro
2007-08-28 12:09 ` Robin Holt
2007-08-28 18:01 ` Christoph Hellwig
2007-08-28 18:01 ` Christoph Hellwig
2007-08-28 18:01 ` Christoph Hellwig
2007-08-27 16:01 ` [PATCH 2/4] export zap_page_range " Dean Nelson
2007-08-27 16:01 ` Dean Nelson
2007-08-27 16:01 ` Dean Nelson
2007-08-27 16:02 ` [PATCH 3/4] add new lock ordering rule to mm/filemap.c Dean Nelson
2007-08-27 16:02 ` Dean Nelson
2007-08-27 16:02 ` Dean Nelson
2007-08-27 16:41 ` [PATCH 4/4] add SGI Altix cross partition memory (XPMEM) driver Dean Nelson
2007-08-27 16:41 ` Dean Nelson
2007-08-27 20:00 ` Adrian Bunk
2007-08-27 20:00 ` Adrian Bunk
2007-08-27 20:00 ` Adrian Bunk
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:05 ` Christoph Hellwig
2007-08-28 19:05 ` Christoph Hellwig
2007-08-28 19:05 ` Christoph Hellwig
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=20070827155933.GB25589@sgi.com \
--to=dcn@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.