From: Andrew Morton <akpm@zip.com.au>
To: maneesh@in.ibm.com
Cc: LKML <linux-kernel@vger.kernel.org>, viro@math.psu.edu
Subject: Re: [RFC] link_path_walk cleanup
Date: Fri, 26 Apr 2002 09:40:28 -0700 [thread overview]
Message-ID: <3CC982FC.C2B6F099@zip.com.au> (raw)
In-Reply-To: <20020426192146.M31039@in.ibm.com>
Maneesh Soni wrote:
>
>..
> +static inline int walk_one(struct nameidata *nd)
This function is hundreds and hundreds of bytes of code. It has
three call sites. Making it an inline is very inefficient!
-
next prev parent reply other threads:[~2002-04-26 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 13:51 [RFC] link_path_walk cleanup Maneesh Soni
2002-04-26 16:40 ` Andrew Morton [this message]
2002-04-26 17:26 ` Alexander Viro
2002-04-27 1:45 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 21:28 Paul Menage
2002-04-29 5:19 ` Maneesh Soni
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=3CC982FC.C2B6F099@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=viro@math.psu.edu \
/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