From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: mmap hw behavior Date: Wed, 08 Jul 2009 10:35:20 -0700 (PDT) Message-ID: <20090708.103520.193697491.davem@davemloft.net> References: <4A54D14F.9090101@petalogix.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:60519 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754066AbZGHRfS (ORCPT ); Wed, 8 Jul 2009 13:35:18 -0400 In-Reply-To: <4A54D14F.9090101@petalogix.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: michal.simek@petalogix.com Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, mingo@elte.hu, arnd@arndb.de, lethal@linux-sh.org, ltp-list@lists.sourceforge.net From: Michal Simek Date: Wed, 08 Jul 2009 19:03:11 +0200 > When I call mmap for that open file with pointer to calloc place > (first parameter, + length zero) it should be one tlb invalidation > for calloc and new tlb which connect open file. We check it and we > don't have any tlb invalidation that's why I think that kernel do > different thigs. Or is it there any copying? Or anything different? There is no need to tlb flush the calloc area unless that memory area is actually touched by the user application and thus the page is faulted in.