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: <1250686586.8282.12.camel@twins>
Date:	Wed, 19 Aug 2009 14:56:26 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
	stephane eranian <eranian@...glemail.com>
Subject: Re: [PATCH 4/4][RFC] perf_counter: Allow sharing of output channels

On Wed, 2009-08-19 at 22:36 +1000, Paul Mackerras wrote:
> Peter Zijlstra writes:
> 
> > Provide the ability to configure a counter to send its output to
> > another (already existing) counter's output stream.
> 
> What sort of thing might this be useful for?

Some people complained that its tedious to mmap() for every counter and
would like to share the mmap() output buffer between counters.

This saves on address space and mlock budget and I guess fd management
logic.

As long as you're not mixing counters for different tasks/cpus there
should be no performance penalty, but even if you do that it might work
well enough on slow samples/small systems..

> Does this only apply to sampling counters?

Yeah, everything that would otherwise go through the mmap() buffer.

I'm not sure there's anything to be done about the read(2) 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ