From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:50200 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754424AbeCVNgJ (ORCPT ); Thu, 22 Mar 2018 09:36:09 -0400 Date: Thu, 22 Mar 2018 09:36:05 -0400 From: Steven Rostedt To: Alexei Starovoitov Cc: Linus Torvalds , David Miller , Daniel Borkmann , Peter Zijlstra , Network Development , kernel-team , Linux API Subject: Re: [PATCH v2 bpf-next 4/8] tracepoint: compute num_args at build time Message-ID: <20180322093605.51b067fe@gandalf.local.home> In-Reply-To: <2559d7cb-ec60-1200-2362-04fa34fd02bb@fb.com> References: <20180321185448.2806324-1-ast@fb.com> <20180321185448.2806324-5-ast@fb.com> <2559d7cb-ec60-1200-2362-04fa34fd02bb@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 21 Mar 2018 15:05:46 -0700 Alexei Starovoitov wrote: > Like the only reason my patch is counting till 17 is because of > trace_iwlwifi_dev_ucode_error(). > The next offenders are using 12 arguments: > trace_mc_event() > trace_mm_vmscan_lru_shrink_inactive() > > Clearly not every efficient usage of it: > trace_mm_vmscan_lru_shrink_inactive(pgdat->node_id, > nr_scanned, nr_reclaimed, > stat.nr_dirty, stat.nr_writeback, > stat.nr_congested, stat.nr_immediate, > stat.nr_activate, stat.nr_ref_keep, > stat.nr_unmap_fail, > sc->priority, file); > could have passed &stat instead. Yes they should have, and if I was on the Cc for that patch, I would have yelled at them and told them that's exactly what they needed to do. Perhaps I should add something to keep any tracepoint from having more than 6 arguments. That should force a clean up quickly. I think I may start doing that. -- Steve