From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932505AbeARPVh (ORCPT ); Thu, 18 Jan 2018 10:21:37 -0500 Received: from verein.lst.de ([213.95.11.211]:34556 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932124AbeARPVg (ORCPT ); Thu, 18 Jan 2018 10:21:36 -0500 Date: Thu, 18 Jan 2018 16:21:34 +0100 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Sagi Grimberg , Keith Busch , Linux Kernel Mailinglist , Hannes Reinecke , Linux NVMe Mailinglist Subject: Re: [PATCH v3 1/2] nvme: add tracepoint for nvme_setup_cmd Message-ID: <20180118152134.GB24168@lst.de> References: <20180117105336.8666-1-jthumshirn@suse.de> <20180117105336.8666-2-jthumshirn@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180117105336.8666-2-jthumshirn@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 17, 2018 at 11:53:35AM +0100, Johannes Thumshirn wrote: > +nvme-core-y := trace.o core.o trace.o should be conditional on CONFIG_TRACEPOINTS. > +TRACE_EVENT(nvme_setup_cmd, > + TP_PROTO(struct nvme_command *cmd), > + TP_ARGS(cmd), > + TP_STRUCT__entry( > + __field(__u8, opcode) > + __field(__u8, flags) > + __field(__u16, cid) > + __field(__le32, nsid) > + __field(__le64, metadata) > + __field_struct( struct nvme_command, cmnd ) This still copies the whole SQE. I think that is way to much to copy, especially given that you also copy many of the fields separately as well.