linux-kernel - Re: [PATCH] fadvise: perform WILLNEED readahead in a workqueue

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:	Fri, 22 Feb 2013 11:45:23 -0500
From:	Phillip Susi <psusi@...ntu.com>
To:	Dave Chinner <david@...morbit.com>
CC:	Eric Wong <normalperson@...t.net>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fadvise: perform WILLNEED readahead in a workqueue

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/15/2012 9:45 PM, Dave Chinner wrote:
> On Sat, Dec 15, 2012 at 12:54:48AM +0000, Eric Wong wrote:
>> Applications streaming large files may want to reduce disk
>> spinups and I/O latency by performing large amounts of readahead
>> up front. Applications also tend to read files soon after opening
>> them, so waiting on a slow fadvise may cause unpleasant latency
>> when the application starts reading the file.
>> 
>> As a userspace hacker, I'm sometimes tempted to create a
>> background thread in my app to run readahead().  However, I
>> believe doing this in the kernel will make life easier for other
>> userspace hackers.
>> 
>> Since fadvise makes no guarantees about when (or even if)
>> readahead is performed, this change should not hurt existing
>> applications.
>> 
>> "strace -T" timing on an uncached, one gigabyte file:
>> 
>> Before: fadvise64(3, 0, 0, POSIX_FADV_WILLNEED) = 0 <2.484832> 
>> After: fadvise64(3, 0, 0, POSIX_FADV_WILLNEED) = 0 <0.000061>
> 
> You've basically asked fadvise() to readahead the entire file if
> it can. That means it is likely to issue enough readahead to fill
> the IO queue, and that's where all the latency is coming from. If
> all you are trying to do is reduce the latency of the first read,
> then only readahead the initial range that you are going to need to
> read...

It shouldn't take 2 seconds to queue up some async reads.  Are you
using ext3?  The blocks have to be mapped in order to queue the reads,
and without ext4 extents, this means the indirect blocks have to be
read and can cause fadvise to block.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRJ6CjAAoJEJrBOlT6nu759s8IAKmIyZYDk1JSRP6oJaGaGZ/r
aZCBH52wTPH8DaqFGe+62L8lyIQ5hD15Y+zTuaWh+fJ7C1k/lU8F/QbKCG2D+xCB
vfLF0WRx63fWLLg8xZTRU1x8X6sG+Byp+UYWNspTDrL15ChlaqqGGmwLNo4JxLa8
+AGQVt1WMU3TitD9CUMUfYFWGUQsMR0gWeJkJnjHiEZ7VoGzft2PTlnvElzIk76u
3cmwfoKHrnXzi50rPtP2gonRjMwd8VY859qOk0zlHoMDMcXklAWeIN9PEUIMx+VP
fMnBm6u48cKXPYGvQrGMOdjxlt7k4LhGDZxIlvmwNHWUSaifmkJ8oBMvfbAYtUA=
=G5rE
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/