[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150511085759.71deeb64@gandalf.local.home>
Date: Mon, 11 May 2015 08:57:59 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Chris Metcalf <cmetcalf@...hip.com>,
Gilad Ben Yossef <giladb@...hip.com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Rik van Riel <riel@...hat.com>, Tejun Heo <tj@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Christoph Lameter <cl@...ux.com>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
linux-doc@...r.kernel.org, linux-api@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] support "dataplane" mode for nohz_full
NO_HZ_LEAVE_ME_THE_FSCK_ALONE!
On Sat, 9 May 2015 09:05:38 +0200
Ingo Molnar <mingo@...nel.org> wrote:
> So I think we should either rename NO_HZ_FULL to NO_HZ_PURE, or keep
> it at NO_HZ_FULL: because the intention of NO_HZ_FULL was always to be
> such a 'zero overhead' mode of operation, where if user-space runs, it
> won't get interrupted in any way.
All kidding aside, I think this is the real answer. We don't need a new
NO_HZ, we need to make NO_HZ_FULL work. Right now it doesn't do exactly
what it was created to do. That should be fixed.
Please lets get NO_HZ_FULL up to par. That should be the main focus.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists