From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@muc.de>
Cc: Yinghai Lu <yinghai.lu@amd.com>,
Muli Ben-Yehuda <muli@il.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64 irq: reset more to default when clear irq_vector for destroy_irq
Date: Sat, 28 Oct 2006 14:06:06 -0600 [thread overview]
Message-ID: <m1r6wsnr2p.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061028172941.GA92790@muc.de> (Andi Kleen's message of "28 Oct 2006 19:29:41 +0200, Sat, 28 Oct 2006 19:29:41 +0200")
Andi Kleen <ak@muc.de> writes:
> On Fri, Oct 27, 2006 at 10:44:36PM -0700, Yinghai Lu wrote:
>> revised version according to Eric. and it can be applied clearly to
>> current Linus's Tree.
>>
>> Clear the irq releated entries in irq_vector, irq_domain and vector_irq
>> instead of clearing irq_vector only. So when new irq is created, it
>> could reuse that vector. (actually is the second loop scanning from
>> FIRST_DEVICE_VECTOR+8). This could avoid the vectors are used up
>> with enough module inserting and removing
>
> Added thanks.
>
> Does i386 need a similar patch?
i386 is good, as it doesn't deal with per cpu vectors, so it doesn't
have the additional data structures.
Eric
next prev parent reply other threads:[~2006-10-28 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 16:40 Lu, Yinghai
2006-10-27 6:20 ` Eric W. Biederman
2006-10-28 5:44 ` Yinghai Lu
2006-10-28 9:18 ` Oleg Verych
2006-10-28 17:29 ` Andi Kleen
2006-10-28 20:06 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 21:33 Lu, Yinghai
2006-10-24 22:52 ` Josef Sipek
2006-10-25 3:46 ` Yinghai Lu
2006-10-25 4:02 ` Yinghai Lu
2006-10-25 4:52 ` David Rientjes
2006-10-25 6:01 ` yhlu
2006-10-25 11:30 ` Muli Ben-Yehuda
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=m1r6wsnr2p.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=yinghai.lu@amd.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
all inboxes | Powered by JetHome®