mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	David Laight <David.Laight@ACULAB.COM>,
	torvalds@linux-foundation.org, tj@kernel.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	ebiederm@xmission.com, neilb@suse.de, bfields@fieldses.org,
	ejt@redhat.com, snitzer@redhat.com, edumazet@google.com,
	josh@joshtriplett.org, rmallon@gmail.com, palves@redhat.com
Subject: Re: [PATCH v6] hashtable: introduce a small and naive hashtable
Date: Thu, 27 Sep 2012 09:30:23 -0400	[thread overview]
Message-ID: <1348752623.22822.73.camel@gandalf.local.home> (raw)
In-Reply-To: <20120927131118.GC30139@Krystal>

On Thu, 2012-09-27 at 09:11 -0400, Mathieu Desnoyers wrote:

> AFAIK, gcc nowadays use "inline" only as a hint

Only if CONFIG_OPTIMIZE_INLINING is set.

>From include/linux/compiler-gcc.h:

#if !defined(CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING) || \
    !defined(CONFIG_OPTIMIZE_INLINING) || (__GNUC__ < 4)
# define inline         inline          __attribute__((always_inline)) notrace
# define __inline__     __inline__      __attribute__((always_inline)) notrace
# define __inline       __inline        __attribute__((always_inline)) notrace
#else
/* A lot of inline functions can cause havoc with function tracing */
# define inline         inline          notrace
# define __inline__     __inline__      notrace
# define __inline       __inline        notrace
#endif

-- Steve



  reply	other threads:[~2012-09-27 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 12:48 Sasha Levin
2012-09-26 13:45 ` David Laight
2012-09-26 13:59   ` Steven Rostedt
2012-09-26 14:26     ` Sasha Levin
2012-09-26 14:39       ` Mathieu Desnoyers
2012-09-26 16:09         ` Steven Rostedt
2012-09-26 16:19           ` Mathieu Desnoyers
2012-09-27  8:25             ` David Laight
2012-09-27  8:33               ` Sasha Levin
2012-09-27 12:09                 ` Steven Rostedt
2012-09-27 13:11                 ` Mathieu Desnoyers
2012-09-27 13:30                   ` Steven Rostedt [this message]
2012-09-27 14:36                   ` David Laight
2012-09-27 13:03               ` Mathieu Desnoyers
2012-09-26 14:31   ` Mathieu Desnoyers

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=1348752623.22822.73.camel@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=David.Laight@ACULAB.COM \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=ebiederm@xmission.com \
    --cc=edumazet@google.com \
    --cc=ejt@redhat.com \
    --cc=josh@joshtriplett.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=neilb@suse.de \
    --cc=palves@redhat.com \
    --cc=rmallon@gmail.com \
    --cc=snitzer@redhat.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®