From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Optimize task_thread_info()
Date: Wed, 25 Jan 2006 09:33:10 +0000 [thread overview]
Message-ID: <200601250933.k0P9XAg22783@unix-os.sc.intel.com> (raw)
In-Reply-To: <200601250234.k0P2Y0g18230@unix-os.sc.intel.com>
Chen, Kenneth wrote on Tuesday, January 24, 2006 6:34 PM
> 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.
Nevermind, someone beat me to it by stunning 12 days!!
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h«03591db110e8d195d381a68692eb37da981cdf
[PATCH] ia64: task_thread_info()
on ia64 thread_info is at the constant offset from task_struct and stack
is embedded into the same beast. Set __HAVE_THREAD_FUNCTIONS, made
task_thread_info() just add a constant.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
prev parent reply other threads:[~2006-01-25 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 2:33 Optimize task_thread_info() Chen, Kenneth W
2006-01-25 9:33 ` Chen, Kenneth W [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=200601250933.k0P9XAg22783@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