| 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
| ||
|
Message-ID: <20110304144059.GS20499@htj.dyndns.org> Date: Fri, 4 Mar 2011 15:40:59 +0100 From: Tejun Heo <tj@...nel.org> To: Denys Vlasenko <vda.linux@...glemail.com> Cc: Oleg Nesterov <oleg@...hat.com>, Roland McGrath <roland@...hat.com>, jan.kratochvil@...hat.com, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org Subject: Re: [RFC] Proposal for ptrace improvements On Fri, Mar 04, 2011 at 03:31:15PM +0100, Denys Vlasenko wrote: > On Fri, Mar 4, 2011 at 3:07 PM, Tejun Heo <tj@...nel.org> wrote: > > Hello, > > > > On Fri, Mar 04, 2011 at 02:59:32PM +0100, Denys Vlasenko wrote: > >> I would rather speed strace up than slow it down further, even if > >> slightly. > > > > The question to ask is at what cost? If mostly unnoticeable slow down > > makes the API cleaner, I'll go that way. Everything is a tradeoff. > > # time sh -c 'ls -lR /usr/share >/dev/null' > real 0m2.633s > > strace without PTRACE_GETSIGINFO: > real 0m47.023s > real 0m48.799s > real 0m47.695s > > strace with PTRACE_GETSIGINFO: > real 0m51.958s > real 0m53.773s > real 0m51.625s Great, numbers, so it's ~10 slow down. Gees, with or without that change, strace(2) is heavy, >18 times slower than without. Maybe it should give up on ptrace and use the new tracing infrastructure? Anyways, thanks a lot for the numbers. Much appreciated. -- tejun -- 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/
Powered by blists - more mailing lists