From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominique Martinet Subject: Re: [PATCH] mm/mincore: allow for making sys_mincore() privileged Date: Thu, 10 Jan 2019 13:24:42 +0100 Message-ID: <20190110122442.GA21216@nautica> References: <20190108044336.GB27534@dastard> <20190109022430.GE27534@dastard> <20190109043906.GF27534@dastard> <20190110004424.GH27534@dastard> <20190110070355.GJ27534@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Linus Torvalds Cc: Dave Chinner , Jiri Kosina , Matthew Wilcox , Jann Horn , Andrew Morton , Greg KH , Peter Zijlstra , Michal Hocko , Linux-MM , kernel list , Linux API List-Id: linux-api@vger.kernel.org Linus Torvalds wrote on Thu, Jan 10, 2019: > (Except, of course, if somebody actually notices outside of tests. > Which may well happen and just force us to revert that commit. But > that's a separate issue entirely). Both Dave and I pointed at a couple of utilities that break with this. nocache can arguably work with the new behaviour but will behave differently; vmtouch on the other hand is no longer able to display what's in cache or not - people use that for example to "warm up" a container in page cache based on how it appears after it had been running for a while is a pretty valid usecase to me. >>From the list Kevin harvested out of the debian code search, the postgresql use case is pretty similar - probe what pages of the database were in cache at shutdown so when you restart it you can preload these and reach "cruse speed" faster. Sure that's probably not billions of users but this all looks fairly valid to me... -- Dominique