linux-kernel - Re: [PATCH] Uninline fork.c/exit.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Oct 2007 11:08:14 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Alexey Dobriyan <adobriyan@...ru>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, devel@...nvz.org
Subject: Re: [PATCH] Uninline fork.c/exit.c

On Mon, 1 Oct 2007 16:15:53 +0400
Alexey Dobriyan <adobriyan@...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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/