Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760705Ab3GZVhT (ORCPT ); Fri, 26 Jul 2013 17:37:19 -0400 Received: from mail-ve0-f177.google.com ([209.85.128.177]:46632 "EHLO mail-ve0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760010Ab3GZVhM (ORCPT ); Fri, 26 Jul 2013 17:37:12 -0400 MIME-Version: 1.0 In-Reply-To: <20130726211844.GB8508@moon> References: <20130726201807.GJ8661@moon> <20130726211844.GB8508@moon> From: Andy Lutomirski Date: Fri, 26 Jul 2013 14:36:51 -0700 Message-ID: Subject: Re: [PATCH] mm: Save soft-dirty bits on file pages To: Cyrill Gorcunov Cc: Linux MM , LKML , Pavel Emelyanov , Andrew Morton , Matt Mackall , Xiao Guangrong , Marcelo Tosatti , KOSAKI Motohiro , Stephen Rothwell Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1186 Lines: 25 On Fri, Jul 26, 2013 at 2:18 PM, Cyrill Gorcunov wrote: > On Fri, Jul 26, 2013 at 01:55:04PM -0700, Andy Lutomirski wrote: >> On Fri, Jul 26, 2013 at 1:18 PM, Cyrill Gorcunov wrote: >> > Andy reported that if file page get reclaimed we loose soft-dirty bit >> > if it was there, so save _PAGE_BIT_SOFT_DIRTY bit when page address >> > get encoded into pte entry. Thus when #pf happens on such non-present >> > pte we can restore it back. >> > >> >> Unless I'm misunderstanding this, it's saving the bit in the >> non-present PTE. This sounds wrong -- what happens if the entire pmd > > It's the same as encoding pgoff in pte entry (pte is not present), > but together with pgoff we save soft-bit status, later on #pf we decode > pgoff and restore softbit back if it was there, pte itself can't disappear > since it holds pgoff information. Isn't that only the case for nonlinear mappings? --Andy -- 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/