From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754680AbdEDObQ (ORCPT ); Thu, 4 May 2017 10:31:16 -0400 Received: from mga06.intel.com ([134.134.136.31]:2789 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754183AbdEDObA (ORCPT ); Thu, 4 May 2017 10:31:00 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,287,1491289200"; d="scan'208";a="82483130" Subject: Re: RFC v2: post-init-read-only protection for data allocated dynamically To: Igor Stoppa , Michal Hocko References: <9200d87d-33b6-2c70-0095-e974a30639fd@huawei.com> <70a9d4db-f374-de45-413b-65b74c59edcb@intel.com> Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org From: Dave Hansen Message-ID: <210752b7-1cbf-2ac3-9f9a-62536dfd24d8@intel.com> Date: Thu, 4 May 2017 07:30:59 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/04/2017 01:17 AM, Igor Stoppa wrote: > Or, let me put it differently: my goal is to not fracture more pages > than needed. > It will probably require some profiling to figure out what is the > ballpark of the memory footprint. This is easy to say, but hard to do. What if someone loads a different set of LSMs, or uses a very different configuration? How could this possibly work generally without vastly over-reserving in most cases? > I might have overlooked some aspect of this, but the overall goal > is to have a memory range (I won't call it zone, to avoid referring to a > specific implementation) which is as tightly packed as possible, stuffed > with all the data that is expected to become read-only. I'm starting with the assumption that a new zone isn't feasible. :)