linux-kernel - Re: [PATCH] mm: terminate shrink

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] [day] [month] [year] [list]

Message-ID: <CAJuCfpE+iM0r3E-eeBGDDo5k=i8qar+im+STfsMG75fc+Vpm6w@mail.gmail.com>
Date:   Thu, 7 Dec 2017 20:40:33 -0800
From:   Suren Baghdasaryan <surenb@...gle.com>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Johannes Weiner <hannes@...xchg.org>, minchan@...nel.org,
        mgorman@...hsingularity.net, ying.huang@...el.com,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        Tim Murray <timmurray@...gle.com>, Todd Kjos <tkjos@...gle.com>
Subject: Re: [PATCH] mm: terminate shrink_slab loop if signal is pending

> According to my traces this 43ms could drop to the average of 11ms and
> worst case 25ms if throttle_direct_reclaim would return true when
> fatal signal is pending but I would like to hear your opinion about
> throttle_direct_reclaim logic.

Digging some more into this I realize my last statement might be
incorrect. Throttling in this situation might not help with the signal
handling delay because of the logic in __alloc_pages_slowpath. I'll
have to experiment with this first, please disregard that last
statement for now.