Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932409AbbELKze (ORCPT ); Tue, 12 May 2015 06:55:34 -0400 Received: from mta-out1.inet.fi ([62.71.2.227]:36572 "EHLO johanna1.rokki.sonera.fi" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932200AbbELKzb (ORCPT ); Tue, 12 May 2015 06:55:31 -0400 RazorGate-KAS: Rate: 5 RazorGate-KAS: {RECEIVED: dynamic ip detected} RazorGate-KAS: Envelope from: RazorGate-KAS: Version: 5.5.3 RazorGate-KAS: LuaCore: 80 2014-11-10_18-01-23 260f8afb9361da3c7edfd3a8e3a4ca908191ad29 RazorGate-KAS: Method: none RazorGate-KAS: Lua profiles 69136 [Nov 12 2014] RazorGate-KAS: Status: not_detected Date: Tue, 12 May 2015 13:54:31 +0300 From: "Kirill A. Shutemov" To: Konstantin Khlebnikov Cc: linux-mm@kvack.org, Naoya Horiguchi , linux-kernel@vger.kernel.org, Andrew Morton , Mark Williamson , Pavel Emelyanov , linux-api@vger.kernel.org, Andy Lutomirski , Vlastimil Babka , Pavel Machek , Mark Seaborn , Linus Torvalds , Daniel James , Finn Grimwood Subject: Re: [PATCH v2 3/3] pagemap: switch to the new format and do some cleanup Message-ID: <20150512105431.GD18365@node.dhcp.inet.fi> References: <20150512090156.24768.2521.stgit@buzz> <20150512094306.24768.51325.stgit@buzz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150512094306.24768.51325.stgit@buzz> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1922 Lines: 44 On Tue, May 12, 2015 at 12:43:06PM +0300, Konstantin Khlebnikov wrote: > This patch removes page-shift bits (scheduled to remove since 3.11) and > completes migration to the new bit layout. Also it cleans messy macro. > > Signed-off-by: Konstantin Khlebnikov > --- > fs/proc/task_mmu.c | 152 ++++++++++++++++--------------------------------- > tools/vm/page-types.c | 29 +++------ > 2 files changed, 58 insertions(+), 123 deletions(-) > > diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c > index 0b7a8ffec95f..66bc7207ce90 100644 > --- a/fs/proc/task_mmu.c > +++ b/fs/proc/task_mmu.c > @@ -710,23 +710,6 @@ const struct file_operations proc_tid_smaps_operations = { > .release = proc_map_release, > }; > > -/* > - * We do not want to have constant page-shift bits sitting in > - * pagemap entries and are about to reuse them some time soon. > - * > - * Here's the "migration strategy": > - * 1. when the system boots these bits remain what they are, > - * but a warning about future change is printed in log; > - * 2. once anyone clears soft-dirty bits via clear_refs file, > - * these flag is set to denote, that user is aware of the > - * new API and those page-shift bits change their meaning. > - * The respective warning is printed in dmesg; > - * 3. In a couple of releases we will remove all the mentions > - * of page-shift in pagemap entries. > - */ Wouldn't it be better to just have v2=1 by default for couple releases to see if anything breaks? This way we can revert easily if regression reported. I guess someone could miss this change coming if he didn't touch clear_refs. -- Kirill A. Shutemov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/