From: Chuck Ebbert <cebbert@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
esandeen@redhat.com, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Unnecessary overhead with stack protector.
Date: Wed, 21 Oct 2009 17:08:35 -0400 [thread overview]
Message-ID: <20091021170835.6cd9bd52@katamari.usersys.redhat.com> (raw)
In-Reply-To: <4ADF5FE2.7070604@redhat.com>
On Wed, 21 Oct 2009 14:24:18 -0500
Eric Sandeen <sandeen@redhat.com> wrote:
>
> Forgive me if I'm not using the right tools to look, but it seems to me
> that in the aggregate, CC_STACKPROTECTOR_ALL has a pretty big impact.
FWIW, I think we'll end up either disabling the stackprotector completely
in Fedora, or at least reverting the patch that adds all that overhead.
next prev parent reply other threads:[~2009-10-21 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 18:35 Unnecessary overhead with stack protector Dave Jones
2009-10-15 19:07 ` Ingo Molnar
2009-10-21 15:50 ` Eric Sandeen
2009-10-21 18:00 ` Arjan van de Ven
2009-10-21 18:59 ` Eric Sandeen
2009-10-21 19:09 ` Eric Sandeen
2009-10-21 19:24 ` Eric Sandeen
2009-10-21 21:08 ` Chuck Ebbert [this message]
2009-10-21 19:16 ` XFS stack overhead Ingo Molnar
2009-10-21 19:21 ` Eric Sandeen
2009-10-21 20:22 ` Chuck Ebbert
2009-10-22 1:26 ` Unnecessary overhead with stack protector Andrew Morton
2009-10-26 16:30 ` Chuck Ebbert
2009-10-26 16:37 ` Andrew Morton
2009-10-26 16:56 ` Chuck Ebbert
2009-10-26 20:03 ` Ingo Molnar
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=20091021170835.6cd9bd52@katamari.usersys.redhat.com \
--to=cebbert@redhat.com \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=esandeen@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sandeen@redhat.com \
--cc=tglx@linutronix.de \
/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