linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Blizek <michi1@michaelblizek.twilightparadox.com>
To: Sri Ram Vemulpali <sri.ram.gmu06@gmail.com>
Cc: Kernel-newbies <kernelnewbies@nl.linux.org>,
	Linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: regarding synchronization code
Date: Sat, 25 Sep 2010 10:48:16 +0200	[thread overview]
Message-ID: <20100925084816.GA2946@michaelblizek.twilightparadox.com> (raw)
In-Reply-To: <AANLkTikhWVuL18zRcPTu2TcEQrv8Bpr4O0eafNsPgNjt@mail.gmail.com>

Hi!

On 18:56 Fri 24 Sep     , Sri Ram Vemulpali wrote:
> Hi all,
> 
>   I am encountering alot macros in the code. I did not understand what
> those macro means.
> 
>   Can anyone explain them and the use of them putting them like that.
> 
>    "unlikely"

likely() and unlikely() are wrappers around gcc extensions to give hints about
whether a given branch will likely be taken or not. When done correctly, this
can improve performance.

>    "always_inline"  -- defined at the signature of the function.

This can be used because "inline" is not always inlined. There should be a gcc
option which causes all inline code to be not inlined.

>    "inline" -- I know inline keyword in compiler is used to place the
> code in to the caller function at the time of compiler, but why
> declared as macro

Where do you see inline declared as a macro?

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ

  parent reply	other threads:[~2010-09-25  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 22:56 regarding synchronization code Sri Ram Vemulpali
2010-09-24 23:58 ` Gregory Haskins
2010-09-25  5:16 ` Dave Hylands
2010-09-25  8:48 ` Michael Blizek [this message]
2010-09-25 17:04   ` Sri Ram Vemulpali
2010-09-26  6:52     ` Bond

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=20100925084816.GA2946@michaelblizek.twilightparadox.com \
    --to=michi1@michaelblizek.twilightparadox.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sri.ram.gmu06@gmail.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).