Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753288Ab2E3Ty2 (ORCPT ); Wed, 30 May 2012 15:54:28 -0400 Received: from mail-gh0-f180.google.com ([209.85.160.180]:43570 "EHLO mail-gh0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752269Ab2E3Ty1 (ORCPT ); Wed, 30 May 2012 15:54:27 -0400 MIME-Version: 1.0 In-Reply-To: References: <1338368529-21784-1-git-send-email-kosaki.motohiro@gmail.com> <20120530184638.GU27374@one.firstfloor.org> <20120530193234.GV27374@one.firstfloor.org> From: KOSAKI Motohiro Date: Wed, 30 May 2012 15:54:06 -0400 Message-ID: Subject: Re: [PATCH 0/6] mempolicy memory corruption fixlet To: Christoph Lameter Cc: Andi Kleen , Linus Torvalds , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Dave Jones , Mel Gorman , stable@vger.kernel.org, hughd@google.com, sivanich@sgi.com 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: 1173 Lines: 26 On Wed, May 30, 2012 at 3:42 PM, Christoph Lameter wrote: > On Wed, 30 May 2012, Andi Kleen wrote: > >> On Wed, May 30, 2012 at 01:50:02PM -0500, Christoph Lameter wrote: >> > On Wed, 30 May 2012, Andi Kleen wrote: >> > >> > > I always regretted that cpusets were no done with custom node lists. >> > > That would have been much cleaner and also likely faster than what we have. >> > >> > Could shared memory policies ignore cpuset constraints? >> >> Only if noone uses cpusets as a "security" mechanism, just for a "soft policy" >> Even with soft policy you could well break someone's setup. > > Well at least lets exempt shared memory from memory migration and memory > policy updates. That seems to be causing many of these issues. Yes, that's right direction, I think. Currently, shmem_set_policy() can't handle nonlinear mapping. vma -> file offset transration is not so easy work and I doubt we should do. -- 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/