From: Oleg Nesterov <oleg@tv-sign.ru>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 2/3] revert "Optimize sys_times for a single threadprocess"
Date: Thu, 23 Feb 2006 02:10:32 +0300 [thread overview]
Message-ID: <43FCEF68.BE296D49@tv-sign.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0602221446080.30219@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
>
> On Thu, 23 Feb 2006, Oleg Nesterov wrote:
>
> > tasklist_lock in sys_times() will be eliminated completely
> > by further patch.
>
> Where is that patch? The patch would simply drop the locks?
Just sent it: "[PATCH 1/6] sys_times: don't take tasklist_lock"
It only drops tasklist_lock, sighand->siglock is still needed,
of course.
Oleg.
prev parent reply other threads:[~2006-02-22 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 22:33 [PATCH 2/3] revert "Optimize sys_times for a single thread process" Oleg Nesterov
2006-02-22 22:47 ` Christoph Lameter
2006-02-22 23:10 ` Oleg Nesterov [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=43FCEF68.BE296D49@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.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
all inboxes | Powered by JetHome®