From: Muli Ben-Yehuda <muli@il.ibm.com>
To: yhlu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@muc.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] x86_64 irq: reuse vector for __assign_irq_vector
Date: Tue, 24 Oct 2006 11:06:19 +0200 [thread overview]
Message-ID: <20061024090619.GD4943@rhun.haifa.ibm.com> (raw)
In-Reply-To: <86802c440610232115r76d98803o4293cdafce1fd95c@mail.gmail.com>
On Mon, Oct 23, 2006 at 09:15:31PM -0700, yhlu wrote:
> in phys flat mode, when using set_xxx_irq_affinity to irq balance from
> one cpu to another, _assign_irq_vector will get to increase last used
> vector and get new vector. this will use up the vector if enough
> set_xxx_irq_affintiy are called. and end with using same vector in
> different cpu for different irq. (that is not what we want, we only
> want to use same vector in different cpu for different irq when more
> than 0x240 irq needed). To keep it simple, the vector should be reused
> instead of getting new vector.
>
> Also according to Eric's review, make it more generic to be used with
> flat mode too.
>
> This patch need to be applied over Eric's irq: cpu_online_map patch.
>
>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Muli Ben-Yehuda <muli@il.ibm.com>
> Signed-off-by: Yinghai Lu <yinghai.lu@amd.com>
Boots fine and survives a quick stress test.
Cheers,
Muli
next prev parent reply other threads:[~2006-10-24 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 4:15 [PATCH] x86_64 irq: reuse vector for __assign_irq_vector yhlu
2006-10-24 9:06 ` Muli Ben-Yehuda [this message]
2006-10-24 17:05 ` Andi Kleen
2006-10-26 9:04 ` Yinghai Lu
2006-10-26 18:10 ` Muli Ben-Yehuda
2006-10-27 2:35 ` Andi Kleen
2006-10-28 17:46 ` Andi Kleen
2006-10-28 18:53 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 18:45 Lu, Yinghai
2006-10-25 4:00 ` Yinghai Lu
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=20061024090619.GD4943@rhun.haifa.ibm.com \
--to=muli@il.ibm.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.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.