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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 7 May 2019 11:12:07 -0500
From:   Probir Roy <proy.cse@...il.com>
To:     linux-ext4@...r.kernel.org
Subject: Locality of extent status tree traversal

Hi,

I am running Phoronix-fio benchmark on Linux kernel 4.18.0-rc5. I
observe the same nodes have been traversed on the extent status tree
in "ext4_es_lookup_extent" function when ext4 write begins. What's the
locality signature of "ext4_es_lookup_extent" in general? Is it
possible that same logical block being looked up repeatedly
(Temporal)? Is it possible that co-located logical blocks are searched
by ext4_es_lookup_extent (spatial)?  Or is it totally random?

-- 
Probir Roy

Powered by blists - more mailing lists