From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Optimize task_thread_info()
Date: Wed, 25 Jan 2006 02:33:59 +0000 [thread overview]
Message-ID: <200601250234.k0P2Y0g18230@unix-os.sc.intel.com> (raw)
Kernel scheduler uses thread_info.cpu heavily, task_cpu(p) is use just
about in every hot scheduler functions. Since thread_info structure
always has constant offset from task_struct, access to member variable
of thread_info can be as simple as adding a constant to task_struct
pointer. Optimize ia64 task_thread_info() to use constant offset. This
saves a memory indirection whenever thread_info structure is used.
Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
--- linux-2.6.15/include/asm-ia64/thread_info.h.orig 2006-01-24 17:59:45.909971596 -0800
+++ linux-2.6.15/include/asm-ia64/thread_info.h 2006-01-24 18:31:05.396276697 -0800
@@ -57,9 +57,11 @@ struct thread_info {
/* how to get the thread information struct from C */
#define current_thread_info() ((struct thread_info *) ((char *) current + IA64_TASK_SIZE))
#define alloc_thread_info(tsk) ((struct thread_info *) ((char *) (tsk) + IA64_TASK_SIZE))
+#define task_thread_info(p) ((struct thread_info *) ((char *) (p) + IA64_TASK_SIZE))
#else
#define current_thread_info() ((struct thread_info *) 0)
#define alloc_thread_info(tsk) ((struct thread_info *) 0)
+#define task_thread_info(p) ((struct thread_info *) 0)
#endif
#define free_thread_info(ti) /* nothing */
@@ -67,6 +69,18 @@ struct thread_info {
#define alloc_task_struct() ((task_t *)__get_free_pages(GFP_KERNEL, KERNEL_STACK_SIZE_ORDER))
#define free_task_struct(tsk) free_pages((unsigned long) (tsk), KERNEL_STACK_SIZE_ORDER)
+#define __HAVE_THREAD_FUNCTIONS
+static inline void setup_thread_stack(struct task_struct *p, struct task_struct *org)
+{
+ *task_thread_info(p) = *task_thread_info(org);
+ task_thread_info(p)->task = p;
+}
+
+static inline unsigned long *end_of_stack(struct task_struct *p)
+{
+ return (unsigned long *) (task_thread_info(p) + 1);
+}
+
#endif /* !__ASSEMBLY */
/*
next reply other threads:[~2006-01-25 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 2:33 Chen, Kenneth W [this message]
2006-01-25 9:33 ` Optimize task_thread_info() Chen, Kenneth W
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=200601250234.k0P2Y0g18230@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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