From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754263AbbCBSDa (ORCPT ); Mon, 2 Mar 2015 13:03:30 -0500 Received: from mga09.intel.com ([134.134.136.24]:24840 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753680AbbCBSD3 (ORCPT ); Mon, 2 Mar 2015 13:03:29 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,676,1418112000"; d="scan'208";a="685686301" Message-ID: <1425319406.20819.9.camel@picadillo> Subject: Re: [PATCH 07/15] mm: Add ___GFP_NOTRACE From: Tom Zanussi To: Alexei Starovoitov Cc: Steven Rostedt , Masami Hiramatsu , Namhyung Kim , Andi Kleen , LKML Date: Mon, 02 Mar 2015 12:03:26 -0600 In-Reply-To: References: <93c67b74d54ffbb3658f0d69865bfb3ad5133a27.1425310176.git.tom.zanussi@linux.intel.com> <20150302113701.2171bdd5@gandalf.local.home> <1425314765.20819.7.camel@picadillo> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2015-03-02 at 09:58 -0800, Alexei Starovoitov wrote: > On Mon, Mar 2, 2015 at 8:46 AM, Tom Zanussi wrote: > > On Mon, 2015-03-02 at 11:37 -0500, Steven Rostedt wrote: > >> On Mon, 2 Mar 2015 10:01:00 -0600 > >> Tom Zanussi wrote: > >> > >> > Add a gfp flag that allows kmalloc() et al to be used in tracing > >> > functions. > >> > > >> > The problem with using kmalloc for tracing is that the tracing > >> > subsystem should be able to trace kmalloc itself, which it can't do > >> > directly because of paths like kmalloc()->trace_kmalloc()->kmalloc() > >> > or kmalloc()->trace_mm_page_alloc()->kmalloc(). > >> > >> This part I don't like at all. Why can't the memory be preallocated > >> when the hist is created (the echo 'hist:...')? > >> > > > > Yeah, I didn't like it either. My original version did exactly what you > > suggest and preallocated an array of entries to 'allocate' from in order > > to avoid the problem. > > > > But I wanted to attempt to use the bpf_map directly, which already uses > > kmalloc internally. My fallback in case this wouldn't fly, which it > > obviously won't, would be to add an option to have the bpf_map code > > preallocate a maximum number of entries or pass in a client-owned array > > for the purpose. I'll do that if I don't hear any better ideas.. > > Tom, I'm still reading through the patch set. > Quick comment for the above. > Currently there are two map types: array and hash. > array type is pre-allocating all memory at map creation time. > hash is allocating on demand. OK, so would it make sense to do the same for the hash type, or at least add an option that does that? Tom