From: Daniel Santos <danielfsantos@att.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Santos <daniel.santos@pobox.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, torvalds@linux-foundation.org
Subject: Re: Please be aware that __always_inline doesn't mean "always inline"!
Date: Wed, 26 Sep 2012 19:03:53 -0500 [thread overview]
Message-ID: <506397E9.1070000@att.net> (raw)
In-Reply-To: <20120926165044.46b8f7d6.akpm@linux-foundation.org>
On 09/26/2012 06:50 PM, Andrew Morton wrote:
> As I mentioned in the other thread, the __always_inline's in fs/namei.c
> (at least) are doing exactly what we want them to do, so some more
> investigation is needed here?
Yes, definitely. When I did some tests on it (to confirm the behavior) a
few months ago, it did behave as advertised. Sounds like this definitely
needs more research. Thanks Andrew.
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Santos <danielfsantos@att.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Santos <daniel.santos@pobox.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, torvalds@linux-foundation.org
Subject: Re: Please be aware that __always_inline doesn't mean "always inline"!
Date: Wed, 26 Sep 2012 19:03:53 -0500 [thread overview]
Message-ID: <506397E9.1070000@att.net> (raw)
In-Reply-To: <20120926165044.46b8f7d6.akpm@linux-foundation.org>
On 09/26/2012 06:50 PM, Andrew Morton wrote:
> As I mentioned in the other thread, the __always_inline's in fs/namei.c
> (at least) are doing exactly what we want them to do, so some more
> investigation is needed here?
Yes, definitely. When I did some tests on it (to confirm the behavior) a
few months ago, it did behave as advertised. Sounds like this definitely
needs more research. Thanks Andrew.
Daniel
next prev parent reply other threads:[~2012-09-27 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 23:20 Please be aware that __always_inline doesn't mean "always inline"! Daniel Santos
2012-09-26 23:50 ` Andrew Morton
2012-09-26 23:50 ` Andrew Morton
2012-09-27 0:03 ` Daniel Santos [this message]
2012-09-27 0:03 ` Daniel Santos
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=506397E9.1070000@att.net \
--to=danielfsantos@att.net \
--cc=akpm@linux-foundation.org \
--cc=daniel.santos@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.