From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, shai@scalex86.org
Subject: Re: [PATCH] Optimize sys_times for a single thread process
Date: Tue, 17 May 2005 18:03:37 -0700 [thread overview]
Message-ID: <20050518010337.GB44089@gaz.sfgoth.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0505171536080.15653@graphe.net>
Christoph Lameter wrote:
> + if (current == next_thread(current)) {
> + /*
> + * Single thread case. We do not need to scan the tasklist
> + * and thus can avoid the read_lock(&task_list_lock). We
> + * also do not need to take the siglock since we
> + * are the only thread in this process
> + */
> + utime = cputime_add(current->signal->utime, current->utime);
> + stime = cputime_add(current->signal->utime, current->stime);
> + cutime = current->signal->cutime;
> + cstime = current->signal->cstime;
> + } else
Maybe #ifdef CONFIG_SMP around this? On uniproc you're still saving the
sti/cli around reading the tsk->signal stuff but that's probably not
enough to warrant the code bloat.
Or maybe this is a small enough amount of code not to matter... just a
suggestion.
-Mitch
next prev parent reply other threads:[~2005-05-18 0:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 22:37 Christoph Lameter
2005-05-17 23:10 ` Andrew Morton
2005-05-18 0:13 ` Christoph Lameter
2005-05-18 0:20 ` Andrew Morton
2005-05-18 1:03 ` Mitchell Blank Jr [this message]
2005-05-18 1:00 ` Christoph Lameter
2005-05-18 9:23 Oleg Nesterov
2005-05-18 22:05 ` Christoph Lameter
2005-05-19 7:05 ` Oleg Nesterov
2005-05-19 14:41 ` Christoph Lameter
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=20050518010337.GB44089@gaz.sfgoth.com \
--to=mitch@sfgoth.com \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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®