All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: manish.jaggi@caviumnetworks.com,
	Julien Grall <julien.grall@linaro.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Draft F] Xen on ARM vITS Handling
Date: Tue, 16 Jun 2015 16:07:00 +0100	[thread overview]
Message-ID: <1434467220.13744.216.camel@citrix.com> (raw)
In-Reply-To: <CALicx6srdrEq0+798_kYxHO-X1HXD+uejRZebmkneDTsRZQLVg@mail.gmail.com>

On Tue, 2015-06-16 at 20:20 +0530, Vijay Kilari wrote:
> On Thu, Jun 11, 2015 at 3:10 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
> > Draft F follows. Also at:
> > http://xenbits.xen.org/people/ianc/vits/draftF.{pdf,html}
> >
> >
> > ## Per-domain `struct pending_irq` for `vLPI`s
> >
> > Internally Xen uses a `struct pending_irq` to track the status of any
> > pending virtual IRQ, including a virtual LPI.
> >
> > Upon domain creation an array of such `struct pending_irq`'s will be
> > allocated to cover the range `8192..nr_lpis` (for the number of LPIs
> > which the guest is configured with) and a pointer this array will be
> > stored in the `struct domain`. The function `irq_to_pending` will be
> > modified to lookup interupts in the LPI range in this array.
> >.
> 
> nr_lpis can be large if more devices are assigned to domain.
> As I was suggesting on #xenarm chat, is it ok to use RB-tree instead of array?
> 
> what should be value for nr_lpis?

It should be user configurable and default to the sum of the number of
events on all devices at start of day.

I think this removes the need for it to be an R-B tree, an array is
tolerable here.

Adding an R-B tree not only has a memory overhead, but it then needs
more complex management when inserting, searching, etc.

Ian.

      reply	other threads:[~2015-06-16 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  9:40 [Draft F] Xen on ARM vITS Handling Ian Campbell
2015-06-11 12:02 ` Ian Campbell
2015-06-12  8:37 ` Vijay Kilari
2015-06-12  8:52   ` Ian Campbell
2015-06-12 13:09     ` Julien Grall
2015-06-12 13:16       ` Ian Campbell
2015-06-12 13:32         ` Julien Grall
2015-06-12 14:05           ` Julien Grall
2015-06-12 14:12             ` Ian Campbell
2015-06-12 14:24           ` Ian Campbell
2015-06-12 17:55             ` Julien Grall
2015-06-16 15:10               ` Ian Campbell
2015-06-16 16:14                 ` Julien Grall
2015-06-12 12:55 ` Ian Campbell
2015-06-12 13:14   ` Julien Grall
2015-06-12 13:26     ` Ian Campbell
2015-06-16 14:50 ` Vijay Kilari
2015-06-16 15:07   ` Ian Campbell [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=1434467220.13744.216.camel@citrix.com \
    --to=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.