From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
hannes@cmpxchg.org, Christoph Lameter <cl@linux.com>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vinmenon@codeaurora.org, shashim@codeaurora.org,
Michal Hocko <mhocko@suse.cz>,
mgorman@suse.de, dave@stgolabs.net, koct9i@gmail.com,
Linux Memory Management List <linux-mm@kvack.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] vmstat: Avoid waking up idle-cpu to service shepherd work
Date: Sat, 28 Mar 2015 10:53:22 +0100 [thread overview]
Message-ID: <20150328095322.GH27490@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAOh2x=nbisppmuBwfLWndyCPKem1N_KzoTxyAYcQuL77T_bJfw@mail.gmail.com>
On Sat, Mar 28, 2015 at 09:48:28AM +0530, Viresh Kumar wrote:
> On Fri, Mar 27, 2015 at 3:00 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Fri, Mar 27, 2015 at 10:16:13AM +0100, Peter Zijlstra wrote:
>
> >> So the issue seems to be that we need base->running_timer in order to
> >> tell if a callback is running, right?
> >>
> >> We could align the base on 8 bytes to gain an extra bit in the pointer
> >> and use that bit to indicate the running state. Then these sites can
> >> spin on that bit while we can change the actual base pointer.
> >
> > Even though tvec_base has ____cacheline_aligned stuck on, most are
> > allocated using kzalloc_node() which does not actually respect that but
> > already guarantees a minimum u64 alignment, so I think we can use that
> > third bit without too much magic.
>
> Right. So what I tried earlier was very much similar to you are suggesting.
> The only difference was that I haven't made much attempts towards
> saving memory.
>
> But Thomas didn't like it for sure and I believe that Rant will hold true for
> what you are suggesting as well, isn't it ?
>
> http://lists.linaro.org/pipermail/linaro-kernel/2013-November/008866.html
Well, for one your patch is indeed disgusting. But yes I'm aware Thomas
wants to rewrite the timer thing. But Thomas is away for a little while
and if this really needs to happen then it does.
Alternatively the thing hocko suggests is an utter fail too. You cannot
stuff that into hardirq context, that's insane.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-03-28 9:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 5:39 Viresh Kumar
2015-03-26 20:18 ` Andrew Morton
2015-03-27 4:49 ` Viresh Kumar
2015-03-27 9:16 ` Peter Zijlstra
2015-03-27 9:30 ` Peter Zijlstra
2015-03-27 11:11 ` Christoph Lameter
2015-03-27 12:02 ` Peter Zijlstra
2015-03-27 19:45 ` Christoph Lameter
2015-03-28 4:28 ` Viresh Kumar
2015-03-28 11:41 ` Peter Zijlstra
2015-03-28 4:18 ` Viresh Kumar
2015-03-28 9:53 ` Peter Zijlstra [this message]
2015-03-28 11:57 ` viresh kumar
2015-03-28 12:04 ` Viresh Kumar
2015-03-28 13:44 ` Peter Zijlstra
2015-03-29 10:24 ` Peter Zijlstra
2015-03-30 12:02 ` Viresh Kumar
2015-03-30 12:47 ` Peter Zijlstra
2015-03-30 13:14 ` Viresh Kumar
2015-03-30 13:59 ` Peter Zijlstra
2015-03-30 16:17 ` Viresh Kumar
2015-03-30 16:25 ` Peter Zijlstra
2015-03-29 12:01 ` Viresh Kumar
2015-03-29 17:24 ` Peter Zijlstra
2015-03-30 15:08 ` Michal Hocko
2015-03-30 15:14 ` Peter Zijlstra
2015-03-30 15:42 ` Christoph Lameter
2015-03-27 14:19 ` Michal Hocko
2015-03-28 4:34 ` Viresh Kumar
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=20150328095322.GH27490@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=koct9i@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=shashim@codeaurora.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=vinmenon@codeaurora.org \
--cc=viresh.kumar@linaro.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