All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: avi@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com,
	paulmck@linux.vnet.ibm.com, markmc@redhat.com
Subject: Re: [PATCH] kvm: remove in_range from kvm_io_device
Date: Tue, 23 Jun 2009 12:14:00 -0400	[thread overview]
Message-ID: <4A40FF48.8030604@novell.com> (raw)
In-Reply-To: <20090623155607.GB21423@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Michael S. Tsirkin wrote:
> On Tue, Jun 23, 2009 at 11:44:57AM -0400, Gregory Haskins wrote:
>   
>>>>  This proposed approach forces us into a
>>>> potential O(256) algorithm in the hotpath (all MMIO/PIO exits will hit
>>>> this, not just in-kernel users).  How would you address this?
>>>>     
>>>>         
>>> Two ideas that come to mind:
>>> - add addr/len fields to devices, use these to speed up lookup
>>>   
>>>       
>> Yep, thats what I was thinking as well.  We can have the top-level
>> (group) be an rbtree on addr/len, and then walk the list of items at
>> that address linearly using your read/write() approach.
>>
>>
>>     
>>> - add a small cache that can be scanned first
>>>   
>>>       
>> Yep, I think we may want to do this anyway independent of the search alg.
>>
>>     
>>> In both cases, you first do a fast lookup, ask the device whether
>>> it wants the transaction, then resort to linear scan if not
>>>   
>>>       
>> -Greg
>>
>>     
>
> Looks like we have a concensus then.
>
>   

Yep.  I'll try to go over the patch in detail today and provide any more
feedback.

Thanks Michael,
-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]

  reply	other threads:[~2009-06-23 16:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 15:00 [PATCH] kvm: remove in_range from kvm_io_device Michael S. Tsirkin
2009-06-23 15:21 ` Gregory Haskins
2009-06-23 15:31   ` Michael S. Tsirkin
2009-06-23 15:44     ` Gregory Haskins
2009-06-23 15:56       ` Michael S. Tsirkin
2009-06-23 16:14         ` Gregory Haskins [this message]
2009-06-24  1:43 ` Gregory Haskins
2009-06-24  8:49   ` Michael S. Tsirkin
2009-06-25 11:08     ` Michael S. Tsirkin
2009-06-25 11:27       ` Gregory Haskins
2009-06-25 11:54         ` Michael S. Tsirkin
2009-06-25 12:08           ` Gregory Haskins
2009-06-25 12:37             ` Michael S. Tsirkin
2009-06-25 13:02               ` Gregory Haskins
2009-06-25 13:16                 ` Michael S. Tsirkin
2009-06-25 13:19                   ` Gregory Haskins
2009-06-28 12:07                     ` Avi Kivity
2009-06-25 15:45       ` Gregory Haskins

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=4A40FF48.8030604@novell.com \
    --to=ghaskins@novell.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=paulmck@linux.vnet.ibm.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.