From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755006AbbIBPSN (ORCPT ); Wed, 2 Sep 2015 11:18:13 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:35629 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753766AbbIBPSL (ORCPT ); Wed, 2 Sep 2015 11:18:11 -0400 Message-ID: <55E7132E.104@plexistor.com> Date: Wed, 02 Sep 2015 18:18:06 +0300 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Dave Hansen , Boaz Harrosh , 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@ml01.01.org, Matthew Wilcox , Peter Zijlstra , Thomas Gleixner , x86@kernel.org 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> In-Reply-To: <55E70653.4090302@linux.intel.com> 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 09/02/2015 05:23 PM, Dave Hansen wrote: <> > I'd be curious what the cost is in practice. Do you have any actual > numbers of the cost of doing it this way? > > Even if the instruction is a "noop", I'd really expect the overhead to > really add up for a tens-of-gigabytes mapping, no matter how much the > CPU optimizes it. What tens-of-gigabytes mapping? I have yet to encounter an application that does that. Our tests show that usually the mmaps are small. I can send you a micro benchmark results of an mmap vs direct-io random write. Our code will jump over holes in the file BTW, but I'll ask to also run it with falloc that will make all blocks allocated. Give me a few days to collect this. I guess one optimization we should do is jump over holes and zero-extents. This will save the case of a mostly sparse very big file. Thanks Boaz