From: Alexey Dobriyan <adobriyan@sw.ru>
To: Arjan van de Ven <arjan@infradead.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Uninline fork.c/exit.c
Date: Tue, 2 Oct 2007 10:40:55 +0400 [thread overview]
Message-ID: <20071002064055.GA6144@localhost.sw.ru> (raw)
In-Reply-To: <20071001110814.4e137e03@laptopd505.fenrus.org>
On Mon, Oct 01, 2007 at 11:08:14AM -0700, Arjan van de Ven wrote:
> On Mon, 1 Oct 2007 16:15:53 +0400
> Alexey Dobriyan <adobriyan@sw.ru> wrote:
>
> > Save ~650 bytes here.
> >
> > add/remove: 4/0 grow/shrink: 0/7 up/down: 430/-1088 (-658)
> > function old new delta
> > __copy_fs_struct - 202 +202
> > __put_fs_struct - 112 +112
> > __exit_fs - 58 +58
> > __exit_files - 58 +58
> > exit_files 58 2 -56
> > put_fs_struct 112 5 -107
> > exit_fs 161 2 -159
> > sys_unshare 774 590 -184
> > copy_process 4031 3840 -191
> > do_exit 1791 1597 -194
> > copy_fs_struct 202 5 -197
> >
> > No difference in lmbench lat_proc tests on 2-way Opteron 246.
> > Smaaaal degradation on UP P4 (within errors).
> >
>
> is there any impact on stack usage?
No differences in checkstack output which threshold is 100 bytes.
prev parent reply other threads:[~2007-10-02 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 12:15 [PATCH] Uninline fork.c/exit.c Alexey Dobriyan
2007-10-01 18:08 ` Arjan van de Ven
2007-10-02 6:40 ` Alexey Dobriyan [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=20071002064055.GA6144@localhost.sw.ru \
--to=adobriyan@sw.ru \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.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.