linux-ext4 - Re: e2fsck readahead speedup performance report

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] [day] [month] [year] [list]

Date:	Fri, 8 Aug 2014 21:06:34 -0700
From:	"Darrick J. Wong" <darrick.wong@...cle.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: e2fsck readahead speedup performance report

On Fri, Aug 08, 2014 at 11:56:46PM -0400, Theodore Ts'o wrote:
> Interesting results!
> 
> I noticed that the 1TB SSD did seem to suffer when you went from
> multi-threaded to single-threaded.  Was this a SATA-attached or
> USB-attached SSD?  And any insights about why the SSD seemed to
> require threading for better performance when using readaead?

PCIE, and it might simply be having issues. :/

One thing I haven't looked into is how exactly the kernel maps IO
requests to queue slots -- does each CPU get its own pile of slots to
use up?  I _think_ it does, but it's been a few months since I poked
at mq.  Hmm... max_sectors_kb=128, which isn't unusually odd.  Guess
I'll keep digging.

The other disks seems fairly normal, at least.

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