From: Jeff Garzik <jeff@garzik.org>
To: Ron Mercer <ron.mercer@qlogic.com>
Cc: netdev@vger.kernel.org, linux-driver@qlogic.com
Subject: Re: FW: + qla3xxx-is-bust.patch added to -mm tree
Date: Thu, 13 Jul 2006 13:06:19 -0400 [thread overview]
Message-ID: <44B67D8B.4080303@garzik.org> (raw)
In-Reply-To: <0BB3E5E7462EEA4295BC02D49691DC0722399F@AVEXCH1.qlogic.org>
Ron Mercer wrote:
> Jeff,
>
> Regarding your June 22nd post:
>
>> 14) Surely there is a better way to down the adapter than masking the
>> interrupts and resetting the adapter? If this is ever used in non-MSI
>
>> situations (common in Linux today), there is the possibility of
>> screaming interrupts, in shared-interrupt situations.
>
>
> The actual downing of the adapter frees interrupts before issuing a
> reset. Perhaps you are referring to the ql_reset_work() path? This
> handles chip reset requests generated by the iSCSI driver or iSCSI
> firmware. What you see is that interrupts are masked and reset is
> allowed to continue. I have made a change where the interrupt is freed
> before the reset continues. I will post a new patch that covers all
> issues tomorrow.
Freeing a kernel interrupt reservation does not imply that your hardware
has stopped delivering them... in a shared interrupt situation, the
code sequence
free_irq()
perform some action
could cause the kernel to call _another_ driver's interrupt handling
routine over and over again, until _your_ hardware stops raising the
interrupt condition.
Jeff
next prev parent reply other threads:[~2006-07-13 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 16:57 FW: + qla3xxx-is-bust.patch added to -mm tree Ron Mercer
2006-07-13 17:06 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 18:13 Ron Mercer
2006-06-28 23:07 Ron Mercer
2006-06-28 23:24 ` Andrew Morton
2006-06-29 1:37 ` Jeff Garzik
2006-06-29 3:41 ` Doug Maxey
2006-06-26 19:02 Ron Mercer
2006-06-26 19:24 ` Andrew Morton
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=44B67D8B.4080303@garzik.org \
--to=jeff@garzik.org \
--cc=linux-driver@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.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.