From: Greg KH <gregkh@linuxfoundation.org>
To: Jon Ringle <jon@ringle.org>
Cc: "Ringle, Jonathan" <Jonathan.Ringle@gridpoint.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add option to build with -O3
Date: Wed, 5 Mar 2014 20:43:37 -0800 [thread overview]
Message-ID: <20140306044337.GB5722@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403050230120.24331@jringle-ubuntu>
On Wed, Mar 05, 2014 at 02:32:26AM -0500, Jon Ringle wrote:
> On Wed, 5 Mar 2014, Greg KH wrote:
>
> > On Tue, Mar 04, 2014 at 07:01:49PM -0500, Jon Ringle wrote:
> > > +config CC_OPTIMIZE_FOR_SPEED
> > > + bool "Optimze for speed (-O3)"
> > > + help
> > > + Enabling this option will pass "-O3" to gcc
> > > + resulting in a larger kernel (but possibly faster)
> >
> > Are you sure about that? Have you measured it?
>
> (Resending this message, since it was "destroyed". Hopefully, this is now
> an an acceptable form :)
>
> I do know that there is an improvement performance-wise for my particular
> use-case.
>
> My target is an ARM board being built with gcc-4.8.2. My board has on it a
> sc16is740 that is used as an RS-485 port. The sc16is740 is on the i2c bus,
> so when an interrupt comes in to indicate that there is data available to
> be read, I need to get the data over the i2c bus. I do this on a kthread
> to do this work. The i2c transactions (using i2c-davinci driver) are also
> interrupt driven. I was seeing a lot of lost packets when receiving data
> at only 19200. Adding the -O3 compile option helped in this regard in that
> I am now rarely seeing packet loss.
I'd take this up with the linux-arm developers, that sounds like
something is wrong with your system that a compiler change fixes
problems. Something else must be wrong...
good luck,
greg k-h
next prev parent reply other threads:[~2014-03-06 4:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 0:01 [PATCH] Add option to build with -O3 Jon Ringle
2014-03-05 5:09 ` Greg KH
2014-03-05 5:37 ` Jon Ringle
2014-03-05 6:08 ` Greg KH
2014-03-05 6:19 ` Jon Ringle
2014-03-05 6:31 ` Greg KH
2014-03-05 18:14 ` Valdis.Kletnieks
2014-03-06 13:28 ` Richard Weinberger
2014-03-07 12:39 ` Austin S Hemmelgarn
2014-03-07 12:42 ` Richard Weinberger
2014-03-07 12:51 ` Austin S Hemmelgarn
2014-03-07 13:48 ` Borislav Petkov
2014-03-05 7:32 ` Jon Ringle
2014-03-06 4:43 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 7:36 jon
2014-03-06 12:28 ` Austin S Hemmelgarn
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=20140306044337.GB5722@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jonathan.Ringle@gridpoint.com \
--cc=jon@ringle.org \
--cc=linux-kernel@vger.kernel.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