From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Chris Metcalf <cmetcalf@tilera.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
linux-mm@kvack.org, Pekka Enberg <penberg@kernel.org>,
Matt Mackall <mpm@selenic.com>,
Sasha Levin <levinsasha928@gmail.com>,
Rik van Riel <riel@redhat.com>, Andi Kleen <andi@firstfloor.org>,
Mel Gorman <mel@csn.ul.ie>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Avi Kivity <avi@redhat.com>,
Michal Nazarewicz <mina86@mina86.com>,
Kosaki Motohiro <kosaki.motohiro@gmail.com>,
Milton Miller <miltonm@bga.com>
Subject: Re: [v7 0/8] Reduce cross CPU IPI interference
Date: Wed, 15 Feb 2012 17:19:11 +0200 [thread overview]
Message-ID: <CAOtvUMeo1=P-4g4ACG3MdSMv_pkQJiDEJQ4cuLTEhrUa+kKGyA@mail.gmail.com> (raw)
In-Reply-To: <1329318679.2293.140.camel@twins>
On Wed, Feb 15, 2012 at 5:11 PM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> On Fri, 2012-02-10 at 22:24 +0200, Gilad Ben-Yossef wrote:
> > I think the concept of giving the task some way to know if the tick is
> > disabled or not is nice.
> > Not sure the exact feature and surely not the interface are what we
> > should adopt - maybe
> > allow registering to receive a signal at the end of the tick when it
> > is disabled an re-enabled?
>
> Fair enough, I indeed missed that property. And yes that makes sense.
>
> It might be a tad tricky to implement as things currently stand, because
> AFAICR Frederic's stuff re-enables the tick on kernel entry (syscall)
> things like signal delivery or a blocking wait for it might be 'fun'.
>
> But I'll have to defer to Frederic, its been too long since I've seen
> his patches to remember most details.
Yes, what I had in mind is that since Frederic's patch set always
disables the tick
from inside the (last) timer tick, we can have the tick return to user
code from the timer
with a signal whenever it is disabled or re-enabled. Basically, have
the timer code make
the signal pending from inside the timer, so that the return to user
space on the special
timer ticks (the last before disable or the first after re-enable)
will be to a signal handler.
I don't know if what I wrote above actually makes sense or not :-)
I'll try to hack something
up and see.
Thanks,
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
gilad@benyossef.com
Israel Cell: +972-52-8260388
US Cell: +1-973-8260388
http://benyossef.com
"If you take a class in large-scale robotics, can you end up in a
situation where the homework eats your dog?"
-- Jean-Baptiste Queru
next prev parent reply other threads:[~2012-02-15 15:19 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 10:01 [v7 0/8] Reduce cross CPU IPI interference Gilad Ben-Yossef
2012-01-26 10:01 ` [v7 1/8] smp: introduce a generic on_each_cpu_mask function Gilad Ben-Yossef
2012-01-29 12:24 ` Gilad Ben-Yossef
2012-01-30 21:52 ` Andrew Morton
2012-01-31 6:33 ` Gilad Ben-Yossef
2012-01-26 10:01 ` [v7 2/8] arm: move arm over to generic on_each_cpu_mask Gilad Ben-Yossef
2012-01-26 10:01 ` [v7 3/8] tile: move tile to use " Gilad Ben-Yossef
2012-01-26 10:01 ` [v7 4/8] smp: add func to IPI cpus based on parameter func Gilad Ben-Yossef
2012-01-27 23:57 ` Andrew Morton
2012-01-29 12:04 ` Gilad Ben-Yossef
2012-01-26 10:01 ` [v7 5/8] slub: only IPI CPUs that have per cpu obj to flush Gilad Ben-Yossef
2012-01-26 15:09 ` Christoph Lameter
2012-01-26 10:01 ` [v7 6/8] fs: only send IPI to invalidate LRU BH when needed Gilad Ben-Yossef
2012-01-26 10:02 ` [v7 7/8] mm: only IPI CPUs to drain local pages if they exist Gilad Ben-Yossef
2012-01-26 15:13 ` Christoph Lameter
2012-01-28 0:12 ` Andrew Morton
2012-01-29 12:18 ` Gilad Ben-Yossef
2012-01-30 21:49 ` Andrew Morton
2012-01-31 6:32 ` Gilad Ben-Yossef
2012-01-30 14:59 ` Mel Gorman
2012-01-30 15:14 ` Gilad Ben-Yossef
2012-01-30 15:44 ` Mel Gorman
2012-01-26 10:02 ` [v7 8/8] mm: add vmstat counters for tracking PCP drains Gilad Ben-Yossef
2012-01-26 15:19 ` [v7 0/8] Reduce cross CPU IPI interference Peter Zijlstra
2012-01-29 8:25 ` Gilad Ben-Yossef
2012-02-01 17:04 ` Frederic Weisbecker
2012-02-02 8:46 ` Gilad Ben-Yossef
2012-02-02 15:41 ` Chris Metcalf
2012-02-05 11:46 ` Gilad Ben-Yossef
2012-02-10 18:39 ` Peter Zijlstra
2012-02-10 20:13 ` Gilad Ben-Yossef
2012-02-10 20:29 ` Peter Zijlstra
2012-02-10 20:39 ` Gilad Ben-Yossef
2012-02-10 18:33 ` Peter Zijlstra
2012-02-10 20:33 ` Gilad Ben-Yossef
2012-02-15 21:50 ` Chris Metcalf
2012-02-15 22:15 ` Christoph Lameter
2012-02-15 23:44 ` Chris Metcalf
2012-02-21 1:34 ` Frederic Weisbecker
2012-03-01 18:27 ` Chris Metcalf
2012-02-10 18:38 ` Peter Zijlstra
2012-02-10 20:24 ` Gilad Ben-Yossef
2012-02-15 15:11 ` Peter Zijlstra
2012-02-15 15:19 ` Gilad Ben-Yossef [this message]
2012-02-15 21:51 ` Chris Metcalf
2012-02-02 16:24 ` Frederic Weisbecker
2012-02-02 16:29 ` Christoph Lameter
2012-02-09 15:52 ` Frederic Weisbecker
2012-02-09 15:59 ` Chris Metcalf
2012-02-09 18:11 ` Frederic Weisbecker
2012-02-09 16:26 ` Christoph Lameter
2012-02-09 18:32 ` Frederic Weisbecker
2012-02-01 17:35 ` Peter Zijlstra
2012-02-01 17:57 ` Peter Zijlstra
2012-02-02 9:42 ` Gilad Ben-Yossef
2012-02-01 18:40 ` Paul E. McKenney
2012-02-01 20:06 ` Christoph Lameter
2012-02-01 20:13 ` Paul E. McKenney
2012-02-02 9:34 ` Avi Kivity
2012-02-02 15:34 ` Paul E. McKenney
2012-02-02 16:14 ` Avi Kivity
2012-02-02 17:01 ` Paul E. McKenney
2012-02-02 17:23 ` Avi Kivity
2012-02-02 17:51 ` Paul E. McKenney
2012-02-05 12:16 ` Avi Kivity
2012-02-05 16:59 ` Paul E. McKenney
2012-02-09 15:22 ` Frederic Weisbecker
2012-02-09 16:05 ` Avi Kivity
2012-02-09 18:22 ` Frederic Weisbecker
2012-02-09 23:41 ` Paul E. McKenney
2012-02-10 1:39 ` Frederic Weisbecker
2012-02-14 13:18 ` Avi Kivity
2012-02-21 0:02 ` Frederic Weisbecker
2012-02-02 17:25 ` Christoph Lameter
2012-02-05 12:06 ` Gilad Ben-Yossef
2012-02-06 18:19 ` Christoph Lameter
2012-02-09 15:37 ` Frederic Weisbecker
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='CAOtvUMeo1=P-4g4ACG3MdSMv_pkQJiDEJQ4cuLTEhrUa+kKGyA@mail.gmail.com' \
--to=gilad@benyossef.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@gmail.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=miltonm@bga.com \
--cc=mina86@mina86.com \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=riel@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).