All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] IO: Intelligent device lookup on bus
Date: Thu, 21 Jul 2011 13:05:55 +0300	[thread overview]
Message-ID: <4E27FA03.2070006@redhat.com> (raw)
In-Reply-To: <1311196929.21614.5.camel@lappy>

On 07/21/2011 12:22 AM, Sasha Levin wrote:
> >
> >  Some numbers, please.
> >
>
> I'm not sure how to measure performance in this case. You'd need to
> measure access times to each device before and after the patch, and
> average them.
>

Try registering ~100 PIO ioeventfds, and writing a test case which 
accesses a PIO port that misses all of them, in a loop.  Measure your 
exit rate before an after.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-07-21 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 12:11 [PATCH] IO: Intelligent device lookup on bus Sasha Levin
2011-07-20 12:43 ` Jan Kiszka
2011-07-21  8:43   ` Sasha Levin
2011-07-21  9:49     ` Avi Kivity
2011-07-20 19:41 ` Marcelo Tosatti
2011-07-20 21:22   ` Sasha Levin
2011-07-21 10:05     ` Avi Kivity [this message]

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=4E27FA03.2070006@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mtosatti@redhat.com \
    /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.