From: Oleg Nesterov <oleg@redhat.com>
To: Jason Low <jason.low2@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
terry.rudd@hp.com, Rik van Riel <riel@redhat.com>,
Waiman Long <Waiman.Long@hp.com>,
Scott J Norton <scott.norton@hp.com>
Subject: Re: [RFC PATCH] timer: Improve itimers scalability
Date: Fri, 7 Aug 2015 14:01:14 +0200 [thread overview]
Message-ID: <20150807120114.GB16897@redhat.com> (raw)
In-Reply-To: <1438885310.4833.82.camel@j-VirtualBox>
On 08/06, Jason Low wrote:
>
> On Thu, 2015-08-06 at 16:18 +0200, Oleg Nesterov wrote:
> > > + /*
> > > + * Check for the special case process timers.
> > > + */
> > > + check_cpu_itimer(tsk, &sig->it[CPUCLOCK_PROF], &prof_expires, ptime,
> > > + SIGPROF);
> > > + check_cpu_itimer(tsk, &sig->it[CPUCLOCK_VIRT], &virt_expires, utime,
> > > + SIGVTALRM);
> > > +
> >
> > Not sure I understand this part... looks wrong actually, please note
> > that RLIMIT_CPU block above may need to update prof_expires _after_
> > check_cpu_itimer(), or I am totally confused.
>
> This change isn't critical to the patch, so we can delete this from the
> patch. Though from my understanding, the purpose of prof_expires is to
> collect the earliest prof expire time for when we update
> "sig->cputime_expires.prof_exp". So I think it wouldn't matter which
> order prof_expire gets updated (as long as check_timers_list() is called
> first, since prof_expires gets directly assigned there).
Yes, I missed that check_cpu_itimer() checks "it->expires < *expires"
before it updates *expires.
Thanks for correcting me!
Oleg.
prev parent reply other threads:[~2015-08-07 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 0:29 [RFC PATCH] timer: Improve itimers scalability Jason Low
2015-08-05 9:24 ` Peter Zijlstra
2015-08-05 9:37 ` Peter Zijlstra
2015-08-05 19:44 ` Jason Low
2015-08-06 14:18 ` Oleg Nesterov
2015-08-06 18:21 ` Jason Low
2015-08-07 12:01 ` 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=20150807120114.GB16897@redhat.com \
--to=oleg@redhat.com \
--cc=Waiman.Long@hp.com \
--cc=dave@stgolabs.net \
--cc=fweisbec@gmail.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=scott.norton@hp.com \
--cc=terry.rudd@hp.com \
--cc=umgwanakikbuti@gmail.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