From: Ted Phelps <phelps@gnusto.com>
To: Ben Widawsky <ben@bwidawsk.net>, Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org, Julien Cristau <jcristau@debian.org>
Subject: Re: [PATCH 1/2] drm/i915: add module parameter compiler hints
Date: Thu, 07 Jul 2011 10:48:41 +1000 [thread overview]
Message-ID: <8844.1309999721@orpheus.gnusto.com> (raw)
In-Reply-To: Your message of Wed, 06 Jul 2011 16:16:01 MST. <20110706231601.GA1556@seagal.home>
Ben Widawsky writes:
> On Wed, Jul 06, 2011 at 04:03:14PM -0700, Keith Packard wrote:
> > On Wed, 6 Jul 2011 15:14:52 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> >
> > > -static int i915_modeset =3D -1;
> > > +static int i915_modeset __read_mostly =3D -1;
> >
> > What effect does this have? Performance? Code size? More warnings?
>
> __read_mostly attempts to put variables in a cachelines to make it more
> SMP friendly. I'm not sure if there is a performance impact as a result,
> but made this patch based on feedback from Chris. I've seen no
> regressions on Nexuiz.
A link to an informative LKML discussion on this topic is here:
http://lkml.org/lkml/2007/12/17/43
-Ted
next prev parent reply other threads:[~2011-07-07 0:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 22:14 [PATCH 1/2] drm/i915: add module parameter compiler hints Ben Widawsky
2011-07-06 22:14 ` [PATCH 2/2] drm/i915: provide module parameter description Ben Widawsky
2011-07-07 5:58 ` Chris Wilson
2011-07-07 9:17 ` Chris Wilson
2011-07-06 23:03 ` [PATCH 1/2] drm/i915: add module parameter compiler hints Keith Packard
2011-07-06 23:16 ` Ben Widawsky
2011-07-07 0:37 ` Keith Packard
2011-07-07 16:01 ` Jesse Barnes
2011-07-07 0:48 ` Ted Phelps [this message]
2011-07-07 5:52 ` Chris Wilson
2011-07-13 18:16 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2011-07-13 21:38 Ben Widawsky
2011-07-14 8:08 ` Chris Wilson
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=8844.1309999721@orpheus.gnusto.com \
--to=phelps@gnusto.com \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jcristau@debian.org \
--cc=keithp@keithp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.