From: Mike Frysinger <vapier.adi@gmail.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: David Howells <dhowells@redhat.com>,
David McCullough <davidm@snapgear.com>,
Greg Ungerer <gerg@uclinux.org>, Paul Mundt <lethal@linux-sh.org>,
uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org
Subject: Re: [uClinux-dev] [PATCH] FDPIC: respect PT_GNU_STACK exec markings when creating NOMMU stack
Date: Sat, 28 Nov 2009 13:47:26 -0500 [thread overview]
Message-ID: <8bd0f97a0911281047i25626fc5q622e06fa1d306441@mail.gmail.com> (raw)
In-Reply-To: <1259421863-12777-1-git-send-email-vapier@gentoo.org>
On Sat, Nov 28, 2009 at 10:24, Mike Frysinger wrote:
> The current code will load the stack size and markings, but then only use
> the markings in the MMU code path. The NOMMU code path always passes EXEC
> to the mmap() call. While this doesn't matter to most people during the
> run of the code, it causes a pointless icache flush when starting every
> FDPIC application and by default, that tends to be 128kB of waste.
for some raw numbers:
with my default FDPIC boot (inetd/syslog/watchdog), we icache flush
18,562,124 bytes. with this stack fix, we cut off 3,538,944 bytes
(19% shrinkage).
-mike
next prev parent reply other threads:[~2009-11-28 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 15:24 Mike Frysinger
2009-11-28 18:47 ` Mike Frysinger [this message]
2009-12-02 13:44 ` David Howells
2009-12-02 21:29 ` [uClinux-dev] " Mike Frysinger
2009-12-03 17:58 ` David Howells
2009-12-04 7:07 ` Mike Frysinger
2009-12-04 9:40 ` David Howells
2009-12-04 10:26 ` Mike Frysinger
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=8bd0f97a0911281047i25626fc5q622e06fa1d306441@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=davidm@snapgear.com \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
/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®