From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] tools/virtio/ringtest: add usage example to README
Date: Mon, 6 Jun 2016 09:56:18 +0300 [thread overview]
Message-ID: <201606060656.u566rfnx040508@mx0a-001b2d01.pphosted.com> (raw)
In-Reply-To: <20160524124104.GB4725@rapoport-lnx>
Ping?
On Tue, May 24, 2016 at 03:41:04PM +0300, Mike Rapoport wrote:
> Michael,
>
> Any updates on this?
>
> On Wed, May 04, 2016 at 09:12:55AM +0300, Mike Rapoport wrote:
> > Having typical usage example in the README file is more convinient than in
> > the git history...
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
> > ---
> > tools/virtio/ringtest/README | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/tools/virtio/ringtest/README b/tools/virtio/ringtest/README
> > index 34e94c4..d83707a 100644
> > --- a/tools/virtio/ringtest/README
> > +++ b/tools/virtio/ringtest/README
> > @@ -1,2 +1,6 @@
> > Partial implementation of various ring layouts, useful to tune virtio design.
> > Uses shared memory heavily.
> > +
> > +Typical use:
> > +
> > +# sh run-on-all.sh perf stat -r 10 --log-fd 1 -- ./ring
> > --
> > 1.9.1
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-06-06 6:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 6:12 [PATCH] tools/virtio/ringtest: add usage example to README Mike Rapoport
2016-05-04 6:12 ` [PATCH] tools/virtio/ringtest: fix run-on-all.sh to work without /dev/cpu Mike Rapoport
2016-05-04 6:40 ` Cornelia Huck
2016-05-04 6:40 ` Cornelia Huck
2016-05-04 7:59 ` [PATCH v2] " Mike Rapoport
2016-05-04 7:59 ` Mike Rapoport
2016-05-04 8:14 ` Cornelia Huck
2016-05-04 8:14 ` Cornelia Huck
2016-05-04 10:15 ` [PATCH v3] " Mike Rapoport
2016-05-04 10:24 ` Cornelia Huck
2016-05-24 12:41 ` Mike Rapoport
2016-06-06 6:55 ` Mike Rapoport
2016-06-06 6:55 ` Mike Rapoport
[not found] ` <201606060656.u566rhsn006487@mx0a-001b2d01.pphosted.com>
2016-06-06 13:57 ` Michael S. Tsirkin
2016-06-06 13:57 ` Michael S. Tsirkin
2016-05-04 6:12 ` [PATCH] " Mike Rapoport
2016-05-24 12:41 ` [PATCH] tools/virtio/ringtest: add usage example to README Mike Rapoport
2016-06-06 6:56 ` Mike Rapoport
2016-06-06 6:56 ` Mike Rapoport [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-04 6:12 Mike Rapoport
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=201606060656.u566rfnx040508@mx0a-001b2d01.pphosted.com \
--to=rppt@linux.vnet.ibm.com \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.