All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: manish.jaggi@caviumnetworks.com,
	Julien Grall <julien.grall@linaro.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Draft D] Xen on ARM vITS Handling
Date: Fri, 5 Jun 2015 10:28:17 +0100	[thread overview]
Message-ID: <55716BB1.7070806@citrix.com> (raw)
In-Reply-To: <CALicx6ugOzJ4iHD_1n7OTFj=7apg2s4hvZTf-M9yt0Yprhw4QQ@mail.gmail.com>



On 05/06/2015 07:07, Vijay Kilari wrote:
> On Thu, Jun 4, 2015 at 7:24 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
>> This information shall include at least:
>>
>> - The Device ID of the device.
>> - The maximum number of Events which the device is capable of
>>    generating.
>>
>> When a device is discovered/registered (i.e. when all necessary
>> information is available) then:
>>
>> - `struct its_device` and the embedded `events` array will be
>>    allocated (the latter with `nr_events` elements).
>> - The `struct its_device` will be inserted into a mapping (possibly an
>>    R-B tree) from its physical Device ID to the `struct its`.
>
>     Why not radix tree. It might be better in look up?

The lookup up in the radix tree is in O(k) where k is the size of the 
index (i.e the number of DevID bits).

In the R-B tree, the lookup is in O(log(n)) where n is the number of 
member in the tree.

As we use integer for the index, the R-B tree will be faster (The number 
of PCI device per domain will never be too big).

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-06-05  9:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 13:54 [Draft D] Xen on ARM vITS Handling Ian Campbell
2015-06-04 17:55 ` Julien Grall
2015-06-04 19:08   ` Julien Grall
2015-06-05 10:24   ` Ian Campbell
2015-06-05 12:15     ` Julien Grall
2015-06-05 13:20       ` Ian Campbell
2015-06-05 14:12         ` Julien Grall
2015-06-05  6:07 ` Vijay Kilari
2015-06-05  9:16   ` Ian Campbell
2015-06-05  9:28   ` Julien Grall [this message]
2015-06-05  9:51     ` Ian Campbell
2015-06-05  9:49   ` Ian Campbell
2015-06-05 12:41     ` Vijay Kilari
2015-06-05 13:28       ` Ian Campbell
2015-06-05 15:55         ` Vijay Kilari
2015-06-05 16:38           ` Ian Campbell
2015-06-05 17:11             ` Vijay Kilari
2015-06-08  9:59               ` Ian Campbell

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=55716BB1.7070806@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=vijay.kilari@gmail.com \
    --cc=xen-devel@lists.xen.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.