linux-kernel - Re: madvise(2) MADV

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: <1216210495.5232.47.camel@twins>
Date:	Wed, 16 Jul 2008 14:14:55 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Eric Rannaud <eric.rannaud@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm <linux-mm@...ck.org>,
	riel <riel@...hat.com>
Subject: Re: madvise(2) MADV_SEQUENTIAL behavior

On Tue, 2008-07-15 at 23:03 +0000, Eric Rannaud wrote:
> mm/madvise.c and madvise(2) say:
> 
>  *  MADV_SEQUENTIAL - pages in the given range will probably be accessed
>  *		once, so they can be aggressively read ahead, and
>  *		can be freed soon after they are accessed.
> 
> 
> But as the sample program at the end of this post shows, and as I
> understand the code in mm/filemap.c, MADV_SEQUENTIAL will only increase
> the amount of read ahead for the specified page range, but will not
> influence the rate at which the pages just read will be freed from
> memory.

Correct, various attempts have been made to actually implement this, but
non made it through.

My last attempt was:
  http://lkml.org/lkml/2007/7/21/219

Rik recently tried something else based on his split-lru series:
  http://lkml.org/lkml/2008/7/15/465



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