Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753541AbbEHXL2 (ORCPT ); Fri, 8 May 2015 19:11:28 -0400 Received: from mail-db3on0080.outbound.protection.outlook.com ([157.55.234.80]:19865 "EHLO emea01-db3-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752826AbbEHXLZ (ORCPT ); Fri, 8 May 2015 19:11:25 -0400 Authentication-Results: vger.kernel.org; dkim=none (message not signed) header.d=none; Message-ID: <554D428E.6020702@ezchip.com> Date: Fri, 8 May 2015 19:11:10 -0400 From: Chris Metcalf User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Steven Rostedt , Andrew Morton CC: Gilad Ben Yossef , Ingo Molnar , Peter Zijlstra , Rik van Riel , "Tejun Heo" , Frederic Weisbecker , "Thomas Gleixner" , "Paul E. McKenney" , Christoph Lameter , "Srivatsa S. Bhat" , , , Subject: Re: [PATCH 0/6] support "dataplane" mode for nohz_full References: <1431107927-13998-1-git-send-email-cmetcalf@ezchip.com> <20150508141824.797eb0d89d514e39fd30fffe@linux-foundation.org> <20150508172210.559830a9@gandalf.local.home> In-Reply-To: <20150508172210.559830a9@gandalf.local.home> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [173.76.21.154] X-ClientProxiedBy: BN3PR0401CA0030.namprd04.prod.outlook.com (25.162.159.168) To DB5PR02MB0776.eurprd02.prod.outlook.com (25.161.243.147) X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR02MB0776;UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR02MB1032; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:DB5PR02MB0776;BCL:0;PCL:0;RULEID:;SRVR:DB5PR02MB0776; X-Forefront-PRVS: 0570F1F193 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10009020)(6049001)(6009001)(377454003)(51704005)(479174004)(24454002)(65816999)(77156002)(42186005)(86362001)(50466002)(87976001)(122386002)(62966003)(5001960100002)(33656002)(87266999)(54356999)(19580395003)(83506001)(36756003)(77096005)(15975445007)(40100003)(50986999)(76176999)(80316001)(19580405001)(4001350100001)(117156001)(5001770100001)(47776003)(2950100001)(46102003)(65956001)(189998001)(65806001)(92566002)(66066001)(18886065003);DIR:OUT;SFP:1101;SCL:1;SRVR:DB5PR02MB0776;H:[192.168.1.163];FPR:;SPF:None;MLV:sfv;LANG:en; X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 May 2015 23:11:19.4283 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR02MB0776 X-OriginatorOrg: ezchip.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1807 Lines: 42 On 5/8/2015 5:22 PM, Steven Rostedt wrote: > On Fri, 8 May 2015 14:18:24 -0700 > Andrew Morton wrote: > >> On Fri, 8 May 2015 13:58:41 -0400 Chris Metcalf 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 :-) -- Chris Metcalf, EZChip Semiconductor http://www.ezchip.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/