From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932615AbcHKBcn (ORCPT ); Wed, 10 Aug 2016 21:32:43 -0400 Received: from ipmail05.adl6.internode.on.net ([150.101.137.143]:21144 "EHLO ipmail05.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932111AbcHKBcl (ORCPT ); Wed, 10 Aug 2016 21:32:41 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2ArDQBG1atXIAI1LHldg0WBUoJ5g3mdOIxiiB6BfYYXBAICgWE7EgEBAQEBAQEGAQEBAQEBNwFAhF8BBTocIxAIAxgJJQ8FJQMHGhOIMMJAAQEBAQYCASQehUSFFYE5AYhhBZk8jwiPTYw0g3gkAYJOgW0qModRAQEB Date: Thu, 11 Aug 2016 11:32:23 +1000 From: Dave Chinner To: "Huang, Ying" Cc: Linus Torvalds , LKML , Bob Peterson , Wu Fengguang , LKP , Christoph Hellwig Subject: Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression Message-ID: <20160811013223.GU16044@dastard> References: <20160809143359.GA11220@yexl-desktop> <20160810230840.GS16044@dastard> <87eg5w18iu.fsf@yhuang-mobile.sh.intel.com> <87a8gk17x7.fsf@yhuang-mobile.sh.intel.com> <8760r816wf.fsf@yhuang-mobile.sh.intel.com> <20160811011612.GT16044@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160811011612.GT16044@dastard> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 11, 2016 at 11:16:12AM +1000, Dave Chinner wrote: > I need to see these events: > > xfs_file* > xfs_iomap* > xfs_get_block* > > For both kernels. An example trace from 4.8-rc1 running the command > `xfs_io -f -c 'pwrite 0 512k -b 128k' /mnt/scratch/fooey doing an > overwrite and extend of the existing file ends up looking like: > > $ sudo trace-cmd start -e xfs_iomap\* -e xfs_file\* -e xfs_get_blocks\* > $ sudo cat /sys/kernel/tracing/trace_pipe > <...>-2946 [001] .... 253971.750304: xfs_file_ioctl: dev 253:32 ino 0x84 > xfs_io-2946 [001] .... 253971.750938: xfs_file_buffered_write: dev 253:32 ino 0x84 size 0x40000 offset 0x0 count 0x20000 > xfs_io-2946 [001] .... 253971.750961: xfs_iomap_found: dev 253:32 ino 0x84 size 0x40000 offset 0x0 count 131072 type invalid startoff 0x0 startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751114: xfs_file_buffered_write: dev 253:32 ino 0x84 size 0x40000 offset 0x20000 count 0x20000 > xfs_io-2946 [001] .... 253971.751128: xfs_iomap_found: dev 253:32 ino 0x84 size 0x40000 offset 0x20000 count 131072 type invalid startoff 0x0 startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751234: xfs_file_buffered_write: dev 253:32 ino 0x84 size 0x40000 offset 0x40000 count 0x20000 > xfs_io-2946 [001] .... 253971.751236: xfs_iomap_found: dev 253:32 ino 0x84 size 0x40000 offset 0x40000 count 131072 type invalid startoff 0x0 startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751381: xfs_file_buffered_write: dev 253:32 ino 0x84 size 0x40000 offset 0x60000 count 0x20000 > xfs_io-2946 [001] .... 253971.751415: xfs_iomap_prealloc_size: dev 253:32 ino 0x84 prealloc blocks 128 shift 0 m_writeio_blocks 16 > xfs_io-2946 [001] .... 253971.751425: xfs_iomap_alloc: dev 253:32 ino 0x84 size 0x40000 offset 0x60000 count 131072 type invalid startoff 0x60 startblock -1 blockcount 0x90 > > That's the output I need for the complete test - you'll need to use > a better recording mechanism that this (e.g. trace-cmd record, > trace-cmd report) because it will generate a lot of events. Compress > the two report files (they'll be large) and send them to me offlist. Can you also send me the output of xfs_info on the filesystem you are testing? Cheers, Dave. -- Dave Chinner david@fromorbit.com From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8229055411594706056==" MIME-Version: 1.0 From: Dave Chinner To: lkp@lists.01.org Subject: Re: [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression Date: Thu, 11 Aug 2016 11:32:23 +1000 Message-ID: <20160811013223.GU16044@dastard> In-Reply-To: <20160811011612.GT16044@dastard> List-Id: --===============8229055411594706056== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Aug 11, 2016 at 11:16:12AM +1000, Dave Chinner wrote: > I need to see these events: > = > xfs_file* > xfs_iomap* > xfs_get_block* > = > For both kernels. An example trace from 4.8-rc1 running the command > `xfs_io -f -c 'pwrite 0 512k -b 128k' /mnt/scratch/fooey doing an > overwrite and extend of the existing file ends up looking like: > = > $ sudo trace-cmd start -e xfs_iomap\* -e xfs_file\* -e xfs_get_blocks\* > $ sudo cat /sys/kernel/tracing/trace_pipe > <...>-2946 [001] .... 253971.750304: xfs_file_ioctl: dev 253:= 32 ino 0x84 > xfs_io-2946 [001] .... 253971.750938: xfs_file_buffered_write:= dev 253:32 ino 0x84 size 0x40000 offset 0x0 count 0x20000 > xfs_io-2946 [001] .... 253971.750961: xfs_iomap_found: dev 253= :32 ino 0x84 size 0x40000 offset 0x0 count 131072 type invalid startoff 0x0= startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751114: xfs_file_buffered_write:= dev 253:32 ino 0x84 size 0x40000 offset 0x20000 count 0x20000 > xfs_io-2946 [001] .... 253971.751128: xfs_iomap_found: dev 253= :32 ino 0x84 size 0x40000 offset 0x20000 count 131072 type invalid startoff= 0x0 startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751234: xfs_file_buffered_write:= dev 253:32 ino 0x84 size 0x40000 offset 0x40000 count 0x20000 > xfs_io-2946 [001] .... 253971.751236: xfs_iomap_found: dev 253= :32 ino 0x84 size 0x40000 offset 0x40000 count 131072 type invalid startoff= 0x0 startblock 24 blockcount 0x60 > xfs_io-2946 [001] .... 253971.751381: xfs_file_buffered_write:= dev 253:32 ino 0x84 size 0x40000 offset 0x60000 count 0x20000 > xfs_io-2946 [001] .... 253971.751415: xfs_iomap_prealloc_size:= dev 253:32 ino 0x84 prealloc blocks 128 shift 0 m_writeio_blocks 16 > xfs_io-2946 [001] .... 253971.751425: xfs_iomap_alloc: dev 253= :32 ino 0x84 size 0x40000 offset 0x60000 count 131072 type invalid startoff= 0x60 startblock -1 blockcount 0x90 > = > That's the output I need for the complete test - you'll need to use > a better recording mechanism that this (e.g. trace-cmd record, > trace-cmd report) because it will generate a lot of events. Compress > the two report files (they'll be large) and send them to me offlist. Can you also send me the output of xfs_info on the filesystem you are testing? Cheers, Dave. -- = Dave Chinner david(a)fromorbit.com --===============8229055411594706056==--