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: <20200814131034.f71a91c6827904e12a629e04@linux-foundation.org>
Date:   Fri, 14 Aug 2020 13:10:34 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Zhaoyang Huang <huangzhaoyang@...il.com>
Cc:     Roman Gushchin <klamm@...dex-team.ru>,
        Zhaoyang Huang <zhaoyang.huang@...soc.com>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm : sync ra->ra_pages with bdi->ra_pages

On Fri, 14 Aug 2020 17:03:44 +0800 Zhaoyang Huang <huangzhaoyang@...il.com> wrote:

> Some system(like android) will turbo read during startup via expanding the
> readahead window and then set it back to normal(128kb as usual). However, some
> files in the system process context will keep to be opened since it is opened
> up and has no chance to sync with the updated value as it is almost impossible
> to change the files attached to the inode(processes are unaware of these things)

How about making VM_READAHEAD_PAGES a variable?  Provide a kernel boot
parameter to alter the default setting.  Userspace can then restore the
usual value later in boot?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ