| 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: <201012061523.03108.rusty@rustcorp.com.au> Date: Mon, 6 Dec 2010 15:23:02 +1030 From: Rusty Russell <rusty@...tcorp.com.au> To: "Michael S. Tsirkin" <mst@...hat.com> Cc: virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] tools/virtio: virtio_test tool On Tue, 30 Nov 2010 03:46:37 am Michael S. Tsirkin wrote: > This is the userspace part of the tool: it includes a bunch of stubs for > linux APIs, somewhat simular to linuxsched. This makes it possible to > recompile the ring code in userspace. > > A small test example is implemented combining this with vhost_test > module. > > Signed-off-by: Michael S. Tsirkin <mst@...hat.com> Hi Michael, I'm not sure what the point is of this work? You'll still need to benchmark on real systems, but it's not low-level enough to measure things like cache misses. I'm assuming you're thinking of playing with layout to measure cache behaviour. I was thinking of a complete userspace implementation where either it was run under cachegrind, or each access was wrapped to allow tracking of cachelines to give an exact measure of cache movement under various scenarios (esp. ring mostly empty, ring in steady state, ring mostly full). Cheers, Rusty. -- 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