From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8376C4363A for ; Thu, 22 Oct 2020 07:20:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 91020223FB for ; Thu, 22 Oct 2020 07:20:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2508397AbgJVHUS (ORCPT ); Thu, 22 Oct 2020 03:20:18 -0400 Received: from mga04.intel.com ([192.55.52.120]:17996 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2506110AbgJVHUS (ORCPT ); Thu, 22 Oct 2020 03:20:18 -0400 IronPort-SDR: y+oTQj4MGj2zZ2du1t81kDe1Ze2tA2ngSTvW1jNKT7W/jlOM53bjz/+FHdWVXeE7shPMGQkGJh C3SHx3irjbvA== X-IronPort-AV: E=McAfee;i="6000,8403,9781"; a="164891588" X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="164891588" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Oct 2020 00:20:18 -0700 IronPort-SDR: HKPUXsdiojHBq+Kxn/wWaHAytaZKtSQLPWdo/PK45+s6KBAv2H1kNLcXEygAC5XTkZp47LviMT MGMzIKOkyE3g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="533839360" Received: from linux.intel.com ([10.54.29.200]) by orsmga005.jf.intel.com with ESMTP; 22 Oct 2020 00:20:17 -0700 Received: from [10.249.225.194] (abudanko-mobl.ccr.corp.intel.com [10.249.225.194]) by linux.intel.com (Postfix) with ESMTP id 97C7758058B; Thu, 22 Oct 2020 00:20:15 -0700 (PDT) Subject: Re: [PATCH v2 05/15] perf session: introduce decompressor into trace reader object To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , Jiri Olsa , Alexander Shishkin , Adrian Hunter , Andi Kleen , Peter Zijlstra , Ingo Molnar , linux-kernel References: <1ec29ed6-0047-d22f-630b-a7f5ccee96b4@linux.intel.com> From: Alexey Budankov Organization: Intel Corp. Message-ID: Date: Thu, 22 Oct 2020 10:20:14 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22.10.2020 7:36, Namhyung Kim wrote: > On Thu, Oct 22, 2020 at 1:00 AM Alexey Budankov > wrote: >> >> >> Introduce decompressor to trace reader object so that decompression >> could be executed on per trace file basis separately for every >> trace file located in trace directory. > > I'm slightly uncomfortable with the word 'trace' here as it's > used for other cases like perf trace and ftrace. Maybe we can > change it to 'profile' and/or 'data file'? Let's use "data file" and "data directory" terms then. Thanks, Alexei