From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754396AbbCBSne (ORCPT ); Mon, 2 Mar 2015 13:43:34 -0500 Received: from smtprelay0037.hostedemail.com ([216.40.44.37]:34324 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753749AbbCBSnd (ORCPT ); Mon, 2 Mar 2015 13:43:33 -0500 X-Session-Marker: 6E657665747340676F6F646D69732E6F7267 X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,rostedt@goodmis.org,:::::::::::,RULES_HIT:41:355:379:541:599:800:960:966:973:988:989:1260:1277:1311:1313:1314:1345:1359:1431:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2196:2199:2393:2553:2559:2562:2693:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3870:3871:3872:3873:3874:4250:4385:5007:6261:7875:8660:10004:10400:10848:10967:11026:11232:11658:11914:12517:12519:12663:12740:13069:13148:13230:13311:13357:14096:14097:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: brush37_75f6f111b1524 X-Filterd-Recvd-Size: 2224 Date: Mon, 2 Mar 2015 13:43:29 -0500 From: Steven Rostedt To: Alexei Starovoitov Cc: Tom Zanussi , Masami Hiramatsu , Namhyung Kim , Andi Kleen , LKML Subject: Re: [PATCH 07/15] mm: Add ___GFP_NOTRACE Message-ID: <20150302134329.623e8dce@gandalf.local.home> In-Reply-To: References: <93c67b74d54ffbb3658f0d69865bfb3ad5133a27.1425310176.git.tom.zanussi@linux.intel.com> <20150302113701.2171bdd5@gandalf.local.home> <1425314765.20819.7.camel@picadillo> <1425319406.20819.9.camel@picadillo> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2 Mar 2015 10:12:32 -0800 Alexei Starovoitov wrote: > I'm not sure what would be the meaning of hash map that has all > elements pre-allocated... > As I'm reading your cover letter, I agree, we need to find a way > to call kmalloc_notrace-like from tracepoints. > Not sure that patch 8 style of duplicating the functions is clean. > Can we keep kmalloc/kfree as-is and do something like > if (in_tracepoint()) check inside ftrace_raw_kmalloc* ? I'm strongly against this. You should not be doing anything in a tracepoint that you can't do from NMI context. And calling kmalloc happens to be one of them. Not to mention, kmalloc is a hot path, and tracing must not have any impact on it (no extra if statements). -- Steve > so that kmalloc will be traced but calls to kmalloc from inside > tracepoints will be automatically suppressed ?