linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
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
Subject: Re: mmap hw behavior
Date: Wed, 08 Jul 2009 10:35:20 -0700 (PDT)	[thread overview]
Message-ID: <20090708.103520.193697491.davem@davemloft.net> (raw)
In-Reply-To: <4A54D14F.9090101@petalogix.com>

From: Michal Simek <michal.simek@petalogix.com>
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.

  parent reply	other threads:[~2009-07-08 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 17:03 mmap hw behavior Michal Simek
2009-07-08 17:03 ` Michal Simek
2009-07-08 17:35 ` David Miller [this message]
2009-07-08 18:03   ` Michal Simek
     [not found]     ` <4A54DF6F.1010405-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
2009-07-08 18:06       ` David Miller
2009-07-08 18:06         ` David Miller
2009-07-08 20:22         ` Michal Simek
2009-07-09  1:15           ` David Miller
2009-07-09  5:40             ` Michal Simek
2009-07-09  8:57             ` Michal Simek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090708.103520.193697491.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arnd@arndb.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=michal.simek@petalogix.com \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).