Re: [PATCH 0/6] support "dataplane" mode for nohz_full
[Posted May 13, 2015 by corbet]
| From: |
| "Paul E. McKenney" <paulmck-AT-linux.vnet.ibm.com> |
| To: |
| Steven Rostedt <rostedt-AT-goodmis.org> |
| Subject: |
| Re: [PATCH 0/6] support "dataplane" mode for nohz_full |
| Date: |
| Mon, 11 May 2015 10:19:16 -0700 |
| Message-ID: |
| <20150511171916.GN6776@linux.vnet.ibm.com> |
| Cc: |
| Ingo Molnar <mingo-AT-kernel.org>, Andrew Morton <akpm-AT-linux-foundation.org>, Chris Metcalf <cmetcalf-AT-ezchip.com>, Gilad Ben Yossef <giladb-AT-ezchip.com>, Ingo Molnar <mingo-AT-redhat.com>, Peter Zijlstra <peterz-AT-infradead.org>, Rik van Riel <riel-AT-redhat.com>, Tejun Heo <tj-AT-kernel.org>, Frederic Weisbecker <fweisbec-AT-gmail.com>, Thomas Gleixner <tglx-AT-linutronix.de>, Christoph Lameter <cl-AT-linux.com>, "Srivatsa S. Bhat" <srivatsa.bhat-AT-linux.vnet.ibm.com>, linux-doc-AT-vger.kernel.org, linux-api-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org |
| Archive‑link: | |
Article |
On Mon, May 11, 2015 at 08:57:59AM -0400, Steven Rostedt wrote:
>
> NO_HZ_LEAVE_ME_THE_FSCK_ALONE!
NO_HZ_OVERFLOWING?
Kconfig naming controversy aside, I believe this patchset is addressing
a real need. Might need additional adjustment, but something useful.
Thanx, Paul
> On Sat, 9 May 2015 09:05:38 +0200
> Ingo Molnar <mingo@kernel.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-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html