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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 18 Nov 2010 11:47:17 +0900
From:	Minchan Kim <>
To:	Rik van Riel <>
Cc:	Peter Zijlstra <>,
	KOSAKI Motohiro <>,
	Ben Gamari <>,,,, Wu Fengguang <>
Subject: Re: fadvise DONTNEED implementation (or lack thereof)

On Thu, Nov 18, 2010 at 1:22 AM, Rik van Riel <> wrote:
> On 11/17/2010 05:16 AM, Minchan Kim wrote:
>> Absolutely. But how about rsync's two touch?
>> It can evict working set.
>> I need the time for investigation.
>> Thanks for the comment.
> Maybe we could exempt MADV_SEQUENTIAL and FADV_SEQUENTIAL
> touches from promoting the page to the active list?

The problem is non-mapped file page.
non-mapped file page promotion happens by only mark_page_accessed.
But it doesn't enough information to prevent promotion(ex, vma or file)
Hmm.. Do other guys have any idea?

Here is another idea.
Current problem is following as.
User can use fadivse with FADV_DONTNEED.
But problem is that it can't affect when it meet dirty pages.
So user have to sync dirty page before calling fadvise with FADV_DONTNEED.
It would lose performance.

Let's add some semantic of FADV_DONTNEED.
It invalidates only pages which are not dirty.
If it meets dirty page, let's move the page into inactive's tail or head.
If we move the page into tail, shrinker can move it into head again
for deferred write if it isn't written the backed device.

> Then we just need to make sure rsync uses fadvise properly
> to keep the working set protected from rsync.
> --
> All rights reversed

Kind regards,
Minchan Kim
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists