[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150508161909.308d60e21f6b83b897174276@linux-foundation.org>
Date: Fri, 8 May 2015 16:19:09 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Chris Metcalf <cmetcalf@...hip.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
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
On Fri, 8 May 2015 19:11:10 -0400 Chris Metcalf <cmetcalf@...hip.com> wrote:
> On 5/8/2015 5:22 PM, Steven Rostedt wrote:
> > On Fri, 8 May 2015 14:18:24 -0700
> > Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> >> On Fri, 8 May 2015 13:58:41 -0400 Chris Metcalf <cmetcalf@...hip.com> wrote:
> >>
> >>> A prctl() option (PR_SET_DATAPLANE) is added
> >> Dumb question: what does the term "dataplane" mean in this context? I
> >> can't see the relationship between those words and what this patch
> >> does.
> > I was thinking the same thing. I haven't gotten around to searching
> > DATAPLANE yet.
> >
> > I would assume we want a name that is more meaningful for what is
> > happening.
>
> The text in the commit message and the 0/6 cover letter do try to explain
> the concept. The terminology comes, I think, from networking line cards,
> where the "dataplane" is the part of the application that handles all the
> fast path processing of network packets, and the "control plane" is the part
> that handles routing updates, etc., generally slow-path stuff. I've probably
> just been using the terms so long they seem normal to me.
>
> That said, what would be clearer? NO_HZ_STRICT as a superset of
> NO_HZ_FULL? Or move away from the NO_HZ terminology a bit; after all,
> we're talking about no interrupts of any kind, and maybe NO_HZ is too
> limited in scope? So, NO_INTERRUPTS? USERSPACE_ONLY? Or look
> to vendors who ship bare-metal runtimes and call it BARE_METAL?
> Borrow the Tilera marketing name and call it ZERO_OVERHEAD?
>
> Maybe BARE_METAL seems most plausible -- after DATAPLANE, to me,
> of course :-)
I like NO_INTERRUPTS. Simple, direct.
--
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