From: David Howells <dhowells@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: dhowells@redhat.com, oleg@redhat.com, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/3] Reduce get_current() to the asm-generic implementation where possible
Date: Fri, 21 May 2010 11:13:23 +0100 [thread overview]
Message-ID: <22710.1274436803@redhat.com> (raw)
In-Reply-To: <20100518194753.GA2318@shareable.org>
Jamie Lokier <jamie@shareable.org> wrote:
> Last time I looked, GCC didn't seem to do anything useful with the
> const attribute on inline functions. I.e. no elimination of duplicate calls.
That's something that may change in the future. It doesn't hurt to have it as
far as I can see.
David
prev parent reply other threads:[~2010-05-21 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 16:45 [PATCH 1/3] Reduce get_current() to the asm-generic implementation where possible David Howells
2010-05-18 16:45 ` [PATCH 2/3] Mark the 'current' pointer register read-only when such a thing exists David Howells
2010-05-18 21:05 ` David Miller
2010-05-18 16:45 ` [PATCH 3/3] Make get_current() __attribute__((const)) David Howells
2010-05-18 21:22 ` schedule() && prev/current (Was: [PATCH 3/3] Make get_current() __attribute__((const))) Oleg Nesterov
2010-05-19 6:21 ` Peter Zijlstra
2010-05-19 10:27 ` Oleg Nesterov
2010-05-19 10:37 ` Peter Zijlstra
2010-05-19 12:57 ` [PATCH] schedule: simplify the reacquire_kernel_lock() logic Oleg Nesterov
2010-05-19 13:11 ` Yong Zhang
2010-06-09 10:13 ` [tip:sched/core] sched: Simplify " tip-bot for Oleg Nesterov
2010-05-19 13:07 ` schedule() && prev/current (Was: [PATCH 3/3] Make get_current() __attribute__((const))) Yong Zhang
2010-05-18 17:39 ` [PATCH 1/3] Reduce get_current() to the asm-generic implementation where possible Kyle McMartin
2010-05-18 19:47 ` Jamie Lokier
2010-05-19 6:21 ` Nick Piggin
2010-05-19 11:02 ` Oleg Nesterov
2010-05-21 10:13 ` David Howells [this message]
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=22710.1274436803@redhat.com \
--to=dhowells@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-arch@vger.kernel.org \
--cc=oleg@redhat.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.