All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Reed <mdr@sgi.com>
To: James.Smart@Emulex.Com
Cc: andrew.vasquez@qlogic.com, linux-scsi@vger.kernel.org, hch@lst.de
Subject: Re: 2.6.15-rc4 error messages with multiple qla2300 hba ports on fabric
Date: Mon, 05 Dec 2005 13:06:26 -0600	[thread overview]
Message-ID: <43948FB2.5070902@sgi.com> (raw)
In-Reply-To: <9BB4DECD4CFE6D43AA8EA8D768ED51C21D7B8D@xbl3.emulex.com>



James.Smart@Emulex.Com wrote:
> We recently saw this as well. It's related to the number of targets
> that go away simultaneously.
> 
> There ends up being many delete rport items on the work queue, and 
> when the 1st one stalls to flush the work queues, it starts the 2nd,
> which stops to flush, and so on.
> 
> My inclination is to look at what we have on the work queue and see if we can
> circumvent some of the flush calls.

Snooping the work queue?  That sounds a little, um, like a hack?
If the code is correct, and the end result is correct, is the
test for recursion level and the associated dump_stack() necessary?
(Yeah, I know, newbie questions. :)


Mike

...snip...


  reply	other threads:[~2005-12-05 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 16:47 2.6.15-rc4 error messages with multiple qla2300 hba ports on fabric James.Smart
2005-12-05 19:06 ` Michael Reed [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-07 21:41 James.Smart
     [not found] <B179AE41C1147041AA1121F44614F0B0012AD98D@AVEXCH02.qlogic.org>
2005-12-02 16:41 ` Michael Reed
2005-12-02 17:05   ` Michele Baldessari
2005-12-07 23:54   ` Andrew Vasquez
2005-12-02 15:26 Michael Reed

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=43948FB2.5070902@sgi.com \
    --to=mdr@sgi.com \
    --cc=James.Smart@Emulex.Com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    /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.