From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Keith Packard <keithp@keithp.com>
Cc: Cristau <jcristau@debian.org>,
intel-gfx@lists.freedesktop.org, Julien@freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: add module parameter compiler hints
Date: Thu, 7 Jul 2011 09:01:23 -0700 [thread overview]
Message-ID: <20110707090123.6c08f50c@jbarnes-desktop> (raw)
In-Reply-To: <yunliwbvscj.fsf@aiko.keithp.com>
On Wed, 06 Jul 2011 17:37:16 -0700
Keith Packard <keithp@keithp.com> wrote:
> On Wed, 6 Jul 2011 16:16:01 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> Non-text part: multipart/signed
>
> > I've seen no regressions on Nexuiz.
>
> 'this doesn't seem to hurt any' is hardly a strong recommendation...
If anything, using __read_mostly appropriately should *increase*
performance, not decrease it. But I think we'd have to measure real
hard to notice anything at all for this particular set of changes
(though __read_mostly is definitely the right thing to do).
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-07 16:01 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 [this message]
2011-07-07 0:48 ` Ted Phelps
2011-07-07 5:52 ` Chris Wilson
2011-07-13 18:16 ` Keith Packard
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=20110707090123.6c08f50c@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Julien@freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).