From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tools/virtio: virtio_test tool
Date: Mon, 6 Dec 2010 15:23:02 +1030 [thread overview]
Message-ID: <201012061523.03108.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20101129171637.GC4027@redhat.com>
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@redhat.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.
next prev parent reply other threads:[~2010-12-06 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 17:04 [PATCH 0/2] tools/virtio: virtio_ring testing tool Michael S. Tsirkin
2010-11-29 17:09 ` [PATCH 1/2] vhost test module Michael S. Tsirkin
2010-12-02 19:00 ` Paul E. McKenney
2010-12-02 19:11 ` Michael S. Tsirkin
2010-12-02 19:26 ` Paul E. McKenney
2010-12-02 19:47 ` Michael S. Tsirkin
2010-12-02 23:13 ` Paul E. McKenney
2010-12-02 23:18 ` Michael S. Tsirkin
2010-12-02 23:56 ` Paul E. McKenney
2010-12-04 18:03 ` Paul E. McKenney
2010-11-29 17:16 ` [PATCH 2/2] tools/virtio: virtio_test tool Michael S. Tsirkin
2010-12-06 4:53 ` Rusty Russell [this message]
2010-12-13 17:14 ` Michael S. Tsirkin
2010-12-06 16:37 ` Thiago Farina
2010-12-13 16:58 ` Michael S. Tsirkin
2011-09-07 3:34 ` Zhi Yong Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012061523.03108.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox