From: Li Yang <leoli@freescale.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Zhao Chenhui <b26998@freescale.com>
Subject: Re: [PATCH 2/4] fsl_msi: enable msi allocation in all banks
Date: Mon, 19 Apr 2010 14:46:42 +0800 [thread overview]
Message-ID: <m2o2a27d3731004182346z39532609o1ad03cc92aa1a50f@mail.gmail.com> (raw)
In-Reply-To: <1271645181.14835.46.camel@concordia>
On Mon, Apr 19, 2010 at 10:46 AM, Michael Ellerman
<michael@ellerman.id.au> wrote:
> On Fri, 2010-04-16 at 15:34 +0800, Li Yang wrote:
>> From: Zhao Chenhui <b26998@freescale.com>
>>
>> Put all fsl_msi banks in a linked list. The list of banks then can be
>> traversed when allocating new msi interrupts.
>
> So there are multiple banks, and you just use the first one that has an
> empty slot in it's bitmap?
Yes, currently we are. What allocation algorithm do you think is
better? I don't think spreading the allocation evenly should have any
performance benefit. The point of multiple banks should be better
insulation through multiple OS's, IMHO.
- Leo
next prev parent reply other threads:[~2010-04-19 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 7:34 [PATCH 1/4] fsl_msi: fix the conflict of virt_msir's chip_data Li Yang
2010-04-16 7:34 ` [PATCH 2/4] fsl_msi: enable msi allocation in all banks Li Yang
2010-04-16 7:34 ` [PATCH 3/4] fsl_msi: enable msi sharing through AMP OSes Li Yang
2010-04-16 7:34 ` [PATCH 4/4] mpc8572ds: change camp dtses for MSI sharing Li Yang
2010-04-19 2:34 ` [PATCH 3/4] fsl_msi: enable msi sharing through AMP OSes Michael Ellerman
2010-04-19 6:23 ` Li Yang
2010-04-19 2:46 ` [PATCH 2/4] fsl_msi: enable msi allocation in all banks Michael Ellerman
2010-04-19 6:46 ` Li Yang [this message]
2010-04-19 2:40 ` [PATCH 1/4] fsl_msi: fix the conflict of virt_msir's chip_data Michael Ellerman
2010-04-19 4:50 ` Li Yang
2010-04-19 12:19 ` Kumar Gala
2010-04-20 3:10 ` Li Yang
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=m2o2a27d3731004182346z39532609o1ad03cc92aa1a50f@mail.gmail.com \
--to=leoli@freescale.com \
--cc=b26998@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).