linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/2] Remove a few inlines in fs/namei.c
Date: Tue, 29 Jul 2008 12:33:37 -0700	[thread overview]
Message-ID: <20080729123337.afb5fe4b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080729185537.GI28946@ZenIV.linux.org.uk>

On Tue, 29 Jul 2008 19:55:37 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:

> On Tue, Jul 29, 2008 at 05:52:31PM +0200, Thomas Petazzoni wrote:
> > Uninline may_create() and do_follow_link() and use vfs_follow_link()
> > instead of __vfs_follow_link() in __do_follow_link(). It allows to
> > slightly reduce the size of kernel code:
> > 
> >    text	   data	    bss	    dec	    hex	filename
> > 1114299	 118564	 212992	1445855	 160fdf	vmlinux.old
> > 1112971	 118564	 212992	1444527	 160aaf	vmlinux
> >   -1328       0       0   -1328    -530 +/-

That's a really big difference, considering whereabouts in the 
kernel this is.

> > This patch is part of the Linux Tiny project and has been originally
> > written by Matt Mackall <mpm@selenic.com>
> 
> Absolutely not.  do_follow_link() et.al. are parts of mutual recursion
> loop and we need to reduce the use of kernel *stack*.

Last time someone tried to "fix" this I suggested that we add some
comments explaining the design - why it is the way it is.  And the
time before that.


      reply	other threads:[~2008-07-29 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080729155229.489904417@free-electrons.com>
     [not found] ` <20080729155527.799486507@free-electrons.com>
2008-07-29 18:55   ` [patch 2/2] Remove a few inlines in fs/namei.c Al Viro
2008-07-29 19:33     ` Andrew Morton [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=20080729123337.afb5fe4b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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).