linux-kernel - Re: [PATCH] perf tool: Fix ppid for synthesized fork events

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: <5511D349.7070508@gmail.com>
Date:	Tue, 24 Mar 2015 15:12:41 -0600
From:	David Ahern <dsahern@...il.com>
To:	Don Zickus <dzickus@...hat.com>
CC:	acme@...nel.org, linux-kernel@...r.kernel.org,
	Jiri Olsa <jolsa@...hat.com>, jmario@...hat.com
Subject: Re: [PATCH] perf tool: Fix ppid for synthesized fork events

On 3/24/15 2:10 PM, Don Zickus wrote:
> He does this with and without the patch.  The difference is usually over 50%
> extra time with the patch for both the record timings and report timings.:-(

I find that shocking. The patch only populates ppid and ptid with a 
value read from the file that is already opened and processed. Most of 
the patch is just plumbing the value from the low level function that 
processes the status file back to synthesize_fork.

What benchmark is this? Is it something I can download and run? if so, 
details? site, command, args?

Thanks,
David
--
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/