From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by kanga.kvack.org (Postfix) with ESMTP id A82636B0254 for ; Thu, 3 Sep 2015 02:41:43 -0400 (EDT) Received: by wicge5 with SMTP id ge5so62361058wic.0 for ; Wed, 02 Sep 2015 23:41:43 -0700 (PDT) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com. [209.85.212.175]) by mx.google.com with ESMTPS id ca13si9141190wib.120.2015.09.02.23.41.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Sep 2015 23:41:42 -0700 (PDT) Received: by wicge5 with SMTP id ge5so62360551wic.0 for ; Wed, 02 Sep 2015 23:41:41 -0700 (PDT) Message-ID: <55E7EBA2.50200@plexistor.com> Date: Thu, 03 Sep 2015 09:41:38 +0300 From: Boaz Harrosh MIME-Version: 1.0 Subject: Re: [PATCH] dax, pmem: add support for msync References: <1441047584-14664-1-git-send-email-ross.zwisler@linux.intel.com> <20150831233803.GO3902@dastard> <20150901070608.GA5482@lst.de> <20150901222120.GQ3902@dastard> <20150902031945.GA8916@linux.intel.com> <20150902051711.GS3902@dastard> <55E6CF15.4070105@plexistor.com> <55E70653.4090302@linux.intel.com> <55E7132E.104@plexistor.com> <55E7184B.3020104@linux.intel.com> <55E71D00.4050103@plexistor.com> <55E7217B.2090803@linux.intel.com> In-Reply-To: <55E7217B.2090803@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Dave Hansen , Dave Chinner , Ross Zwisler , Christoph Hellwig , linux-kernel@vger.kernel.org, Alexander Viro , Andrew Morton , "H. Peter Anvin" , Hugh Dickins , Ingo Molnar , "Kirill A. Shutemov" , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org, Matthew Wilcox , Peter Zijlstra , Thomas Gleixner , x86@kernel.org On 09/02/2015 07:19 PM, Dave Hansen wrote: > On 09/02/2015 09:00 AM, Boaz Harrosh wrote: >>>> We are going to have 2-socket systems with 6TB of persistent memory in >>>> them. I think it's important to design this mechanism so that it scales >>>> to memory sizes like that and supports large mmap()s. >>>> >>>> I'm not sure the application you've seen thus far are very >>>> representative of what we want to design for. >>>> >> We have a patch pending to introduce a new mmap flag that pmem aware >> applications can set to eliminate any kind of flushing. MMAP_PMEM_AWARE. > > Great! Do you have a link so that I can review it and compare it to > Ross's approach? > Ha? I have not seen a new mmap flag from Ross, yet I have been off lately so it is logical that I might have missed it. Could you send me a link? (BTW my patch I did not release yet, I'll cc you once its done) Thanks Boaz -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org