linux-kernel - Re: [PATCH 7/8] Remove current_tick

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]

Message-ID: <2c0942db0803150929q7cc628f8h18269f10daec8ab1@mail.gmail.com>
Date:	Sat, 15 Mar 2008 09:29:59 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Roman Zippel" <zippel@...ux-m68k.org>
Cc:	"john stultz" <johnstul@...ibm.com>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 7/8] Remove current_tick_length()

On Fri, Mar 14, 2008 at 9:18 PM, Roman Zippel <zippel@...ux-m68k.org> wrote:
>  > > > Is there any additional rational for this change?
>  > >
>  > > Useless bloat?
>  >
>  > I agree its a trade off. But do you have performance numbers to make the
>  > maintainability trade off worth it? (I admit, it is used in the
>  > timer_interrupt, so it may very well be worth it, but we might want to
>  > check first).
>
>  It depends on the architecture, but it's effects regularly executed code
>  and every byte counts.

Then make the original function an inline. With -O2 it should compile
to exactly the same thing.
--
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/