From: Rik van Riel <riel@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Frank Mayhar <fmayhar@google.com>,
Frederic Weisbecker <fweisbec@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sanjay Rao <srao@redhat.com>, Larry Woodman <lwoodman@redhat.com>
Subject: Re: [PATCH RFC] time: drop do_sys_times spinlock
Date: Wed, 13 Aug 2014 14:25:53 -0400 [thread overview]
Message-ID: <53EBADB1.2020403@redhat.com> (raw)
In-Reply-To: <20140813180807.GA8098@redhat.com>
On 08/13/2014 02:08 PM, Oleg Nesterov wrote:
> On 08/13, Rik van Riel wrote:
>>
>> On Wed, 13 Aug 2014 19:22:30 +0200
>> Oleg Nesterov <oleg@redhat.com> wrote:
>>
>>> On 08/12, Rik van Riel wrote:
>>>>
>>>> Any other ideas?
>>>
>>> To simplify, lets suppose that we only need sum_exec_runtime.
>>>
>>> Perhaps we can do something like this
>>
>> That would probably work, indeed.
>
> OK, perhaps I'll try to make a patch tomorrow for review.
>
>> However, it turns out that a seqcount doesn't look too badly either.
>
> Well, I disagree. This is more complex, and this adds yet another lock
> which only protects the stats...
The other lock is what can tell us that there is a writer active
NOW, which may be useful when it comes to guaranteeing forward
progress for readers when there are lots of threads exiting...
>> --- a/include/linux/sched.h
>> +++ b/include/linux/sched.h
>> @@ -461,6 +461,7 @@ struct sighand_struct {
>> atomic_t count;
>> struct k_sigaction action[_NSIG];
>> spinlock_t siglock;
>> + seqcount_t stats_seq; /* write nests inside spinlock */
>
> No, no, at least it should go to signal_struct. Unlike ->sighand, ->signal
> is stable as long as task_struct can't go away.
I can move it to signal_struct, no problem.
>> void thread_group_cputime(struct task_struct *tsk, struct task_cputime *times)
>> {
>> struct signal_struct *sig = tsk->signal;
>> + struct sighand_struct *sighand;
>> cputime_t utime, stime;
>> struct task_struct *t;
>> -
>> - times->utime = sig->utime;
>> - times->stime = sig->stime;
>> - times->sum_exec_runtime = sig->sum_sched_runtime;
>> + int seq;
>>
>> rcu_read_lock();
>> - /* make sure we can trust tsk->thread_group list */
>> - if (!likely(pid_alive(tsk)))
>> + sighand = rcu_dereference(tsk->sighand);
>> + if (unlikely(!sighand))
>> goto out;
>>
>> - t = tsk;
>> do {
>> - task_cputime(t, &utime, &stime);
>> - times->utime += utime;
>> - times->stime += stime;
>> - times->sum_exec_runtime += task_sched_runtime(t);
>> - } while_each_thread(tsk, t);
>> + seq = read_seqcount_begin(&sighand->stats_seq);
>> + times->utime = sig->utime;
>> + times->stime = sig->stime;
>> + times->sum_exec_runtime = sig->sum_sched_runtime;
>> +
>> + /* make sure we can trust tsk->thread_group list */
>> + if (!likely(pid_alive(tsk)))
>> + goto out;
>
> Whatever we do, we should convert thread_group_cputime() to use
> for_each_thread() first().
What is the advantage of for_each_thread over while_each_thread,
besides getting rid of that t = tsk line?
>> @@ -781,14 +781,14 @@ static void posix_cpu_timer_get(struct k_itimer *timer, struct itimerspec *itp)
>> cpu_clock_sample(timer->it_clock, p, &now);
>> } else {
>> struct sighand_struct *sighand;
>> - unsigned long flags;
>>
>> /*
>> * Protect against sighand release/switch in exit/exec and
>> * also make timer sampling safe if it ends up calling
>> * thread_group_cputime().
>> */
>> - sighand = lock_task_sighand(p, &flags);
>> + rcu_read_lock();
>> + sighand = rcu_dereference(p->sighand);
>
> This looks unneeded at first glance.
You are right. This change should be made to posix_cpu_clock_get_task
and not posix_cpu_timer_get. I think this is where I got distracted
by the way the sighand struct was RCU freed.
Sigh...
next prev parent reply other threads:[~2014-08-13 18:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 18:25 [PATCH RFC] time: drop do_sys_times spinlock Rik van Riel
2014-08-12 19:12 ` Oleg Nesterov
2014-08-12 19:22 ` Rik van Riel
2014-08-12 22:27 ` Rik van Riel
2014-08-13 17:22 ` Oleg Nesterov
2014-08-13 17:35 ` Rik van Riel
2014-08-13 18:08 ` Oleg Nesterov
2014-08-13 18:25 ` Rik van Riel [this message]
2014-08-13 18:45 ` Oleg Nesterov
2014-08-13 18:57 ` Rik van Riel
2014-08-13 21:03 ` [PATCH RFC] time,signal: protect resource use statistics with seqlock Rik van Riel
2014-08-14 0:43 ` Frederic Weisbecker
2014-08-14 1:57 ` Rik van Riel
2014-08-14 13:34 ` Frederic Weisbecker
2014-08-14 14:39 ` Oleg Nesterov
2014-08-15 2:52 ` Frederic Weisbecker
2014-08-15 14:26 ` Oleg Nesterov
2014-08-15 22:33 ` Frederic Weisbecker
2014-08-14 13:22 ` Oleg Nesterov
2014-08-14 13:38 ` Frederic Weisbecker
2014-08-14 13:53 ` Oleg Nesterov
2014-08-14 17:48 ` Oleg Nesterov
2014-08-14 18:34 ` Oleg Nesterov
2014-08-15 5:19 ` Mike Galbraith
2014-08-15 6:28 ` Peter Zijlstra
2014-08-15 9:37 ` Mike Galbraith
2014-08-15 9:44 ` Peter Zijlstra
2014-08-15 16:36 ` Oleg Nesterov
2014-08-15 16:49 ` Oleg Nesterov
2014-08-15 17:25 ` Rik van Riel
2014-08-15 18:36 ` Oleg Nesterov
2014-08-14 14:24 ` Oleg Nesterov
2014-08-14 15:37 ` Rik van Riel
2014-08-14 16:12 ` Oleg Nesterov
2014-08-14 17:36 ` Rik van Riel
2014-08-14 18:15 ` Oleg Nesterov
2014-08-14 19:03 ` Rik van Riel
2014-08-14 19:37 ` Oleg Nesterov
2014-08-15 2:14 ` Rik van Riel
2014-08-15 14:58 ` Oleg Nesterov
2014-08-13 21:03 ` Rik van Riel
2014-08-13 17:40 ` [PATCH RFC] time: drop do_sys_times spinlock Peter Zijlstra
2014-08-13 17:50 ` Rik van Riel
2014-08-13 17:53 ` Peter Zijlstra
2014-08-13 6:59 ` Mike Galbraith
2014-08-13 11:11 ` Peter Zijlstra
2014-08-13 13:24 ` Rik van Riel
2014-08-13 13:39 ` Peter Zijlstra
2014-08-13 14:09 ` Mike Galbraith
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=53EBADB1.2020403@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fmayhar@google.com \
--cc=fweisbec@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=srao@redhat.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