From: "Jan Beulich" <JBeulich@novell.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Allen M Kay <allen.m.kay@intel.com>
Subject: [PATCH 0/2, v2] replace irq <-> pirq mapping array with radix trees
Date: Tue, 03 May 2011 15:07:07 +0100 [thread overview]
Message-ID: <4DC0282B020000780003F68C@vpn.id2.novell.com> (raw)
This is to further eliminate non-order-zero runtime allocations.
1: x86: replace nr_irqs sized per-domain arrays with radix trees
2: replace d->nr_pirqs sized arrays with radix tree
The first patch can probably go in right away, for the second my
testing abilities are somewhat limited, and hence it may need to be
considered to wait for e.g. Intel to conduct some more testing (otoh
we're early in the release cycle, so eventual fixes could of course
also be carried out as follow-up patches).
v2: Split setup/teardown into two stages - (de-)allocation (tree node
(de-)population) is done with just d->event_lock held (and hence
interrupts enabled), while actual insertion/removal of translation data
gets done with irq_desc's lock held (and interrupts disabled).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
reply other threads:[~2011-05-03 14:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DC0282B020000780003F68C@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=allen.m.kay@intel.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).