linux-ext4 - Re: Filesystem benchmarks on reasonably fast hardware

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]

Message-ID: <20110726145736.GA7684@thunk.org>
Date:	Tue, 26 Jul 2011 10:57:36 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Jörn Engel <joern@...fs.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: Filesystem benchmarks on reasonably fast hardware

On Mon, Jul 25, 2011 at 08:20:37PM +0200, Jörn Engel wrote:
> On Mon, 25 July 2011 11:18:25 -0400, Ted Ts'o wrote:
> > 
> > Did you have a chance to do an ext4 lockstat run?

Hi Jörn,

Thanks for forwarding it to me.  It's the same problem as in XFS, the
excessive coverage of the i_mutex lock.  In ext4's case, it's in the
generic generic_file_aio_write() machinery where we need to do the
lock busting.  (XFS apparently doesn't use the generic routines, so
the fix that Dave did won't help ext3 and ext4.)

I don't have the time to look at it now, but I'll put it on my todo
list; or maybe someone with a bit more time can look into how we might
be able to use a similar approach in the generic file system code.

   	       	 	 	     	 	 - Ted
--
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