From: "Aubrey Li" <aubreylee@gmail.com>
To: "David Howells" <dhowells@redhat.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
vapier.adi@gmail.com, jie.zhang@analog.com, bryan.wu@analog.com,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nommu arch dont zero the anonymous mapping by adding UNINITIALIZE flag
Date: Fri, 30 Mar 2007 23:46:31 +0800 [thread overview]
Message-ID: <6d6a94c50703300846x605e66e0pbd8537a06436f6ee@mail.gmail.com> (raw)
In-Reply-To: <12871.1175267477@redhat.com>
On 3/30/07, David Howells <dhowells@redhat.com> wrote:
> Aubrey Li <aubreylee@gmail.com> wrote:
>
> > Keep the same behave as MMU but with bad performance, or keep the same
> > performance as MMU but without the same behave, Which one is more
> > important?
>
> The thing to do is to pass a flag to mmap() to suppress the memset (as
> suggested). This can then be used by the uClibc malloc() implementation and
> does not impact any application that does an anon mmap() expecting the memory
> returned to be zeroed.
>
As Mike mentioned, it implies breakage in POSIX behavior
and is specific to no-mmu only.
What kind of application does an anonymous mmap() expecting the memory
returned to be zeroed?
-Aubrey
next prev parent reply other threads:[~2007-03-30 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 3:42 Wu, Bryan
2007-03-30 3:53 ` Mike Frysinger
2007-03-30 9:39 ` David Howells
2007-03-30 10:34 ` Aubrey Li
2007-03-30 11:24 ` David Howells
2007-03-30 13:44 ` Aubrey Li
2007-03-30 14:56 ` Alan Cox
2007-03-30 14:38 ` Aubrey Li
2007-03-30 18:13 ` Alan Cox
2007-03-30 15:11 ` David Howells
2007-03-30 15:46 ` Aubrey Li [this message]
2009-10-13 7:44 ` [PATCH] NOMMU: fix malloc performance by adding uninitialized flag Mike Frysinger
2009-10-13 15:20 ` [uClinux-dev] [PATCH] NOMMU: fix malloc performance by addinguninitialized flag Robin Getz
2009-10-13 10:10 ` [PATCH] NOMMU: fix malloc performance by adding uninitialized flag David Howells
2009-10-13 11:20 ` [PATCH v2] " Mike Frysinger
2009-10-13 13:03 ` Paul Mundt
2009-10-13 16:03 ` David Howells
2009-10-13 21:31 ` [PATCH v3] " Mike Frysinger
2009-10-13 23:04 ` David McCullough
2009-10-14 0:25 ` Greg Ungerer
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=6d6a94c50703300846x605e66e0pbd8537a06436f6ee@mail.gmail.com \
--to=aubreylee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=dhowells@redhat.com \
--cc=jie.zhang@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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
all inboxes | Powered by JetHome®