lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 4 Sep 2014 20:10:48 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-ext4@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PATCH v3 2/6] ext4: track extent status tree shrinker delay
 statictics

On Wed, Aug 27, 2014 at 03:26:07PM +0200, Jan Kara wrote:
> On Thu 07-08-14 11:35:49, Zheng Liu wrote:
> > From: Zheng Liu <wenqing.lz@...bao.com>
> > 
> > This commit adds some statictics in extent status tree shrinker.  The
> > purpose to add these is that we want to collect more details when we
> > encounter a stall caused by extent status tree shrinker.  Here we count
> > the following statictics:
> >   stats:
> >     the number of all objects on all extent status trees
> >     the number of reclaimable objects on lru list
> >     cache hits/misses
> >     the last sorted interval
> >     the number of inodes on lru list
> >   average:
> >     scan time for shrinking some objects
> >     the number of shrunk objects
> >   maximum:
> >     the inode that has max nr. of objects on lru list
> >     the maximum scan time for shrinking some objects
> > 
> > The output looks like below:
> >   $ cat /proc/fs/ext4/sda1/es_shrinker_info
> >   stats:
> >     28228 objects
> >     6341 reclaimable objects
> >     5281/631 cache hits/misses
> >     586 ms last sorted interval
> >     250 inodes on lru list
> >   average:
> >     153 us scan time
> >     128 shrunk objects
> >   maximum:
> >     255 inode (255 objects, 198 reclaimable)
> >     125723 us max scan time
>   When reading through this again, I realized that we probably don't want
> this file in /proc/fs/ext4 but rather in /sys/kernel/debug/ext4 because
> it's really a debugging interface and we don't want any tools to start
> using it.

Fair enough.  I will fix it in next version.

Thanks,
                                                - Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ