All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-scsi@vger.kernel.org, linux-driver@qlogic.com,
	james.smart@emulex.com
Subject: Re: [RFC] Asynchronous scanning for FC/SAS version 3
Date: Wed, 22 Nov 2006 10:51:25 -0700	[thread overview]
Message-ID: <20061122175125.GW18567@parisc-linux.org> (raw)
In-Reply-To: <20061122161926.GC1538@andrew-vasquezs-computer.local>

On Wed, Nov 22, 2006 at 08:19:26AM -0800, Andrew Vasquez wrote:
> > This seems like a nice cleanup of some moderately complicated code.
> > We still need scan_start and scan_finished methods so that the midlayer
> > knows when the qla2xxx driver thinks it's found all the devices there
> > are to find.
> 
> BTW:  side-note, this is a bit tricky, as we are dealing with a fabric
> environment where ports can fall on/off a topology at any given time
> (ISL removed, port disconnected, etc. can all cause a loss in fcport
> visibility).

Oh yes, I understand that.  I'm only trying to solve the situation where
the fabric is stable.

> What this condition in scan_finished() is going to
> catch:
> 
> +static int
> +qla2xxx_scan_finished(struct Scsi_Host *shost, unsigned long time)
> +{
> +       scsi_qla_host_t *ha = (scsi_qla_host_t *)shost->hostdata;
> +
> +       if (!ha->host)
> +               return 1;
> +       if (time > ha->loop_reset_delay * HZ)
> +               return 1;
> +
> +       return atomic_read(&ha->loop_state) == LOOP_READY;
> +}
> 
> is the *first* instance where the firmware/driver has attained a
> steady link state within the topology.  The 'found all the devices
> there are to find' case may or may not fall within this window...

Ah, fair point, I didn't *quite* understand the distinction between the
various flags; can you suggest a better condition to test?

> Ok, I've tweaked the code a bit and have been testing with the
> following two patches, the first is a cleaned-up revision of my
> 'alternate' proposal (from above).  The second, adds callbacks for
> your scan_start/end() work.

Thanks a lot!

  parent reply	other threads:[~2006-11-22 17:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 15:26 [RFC] Asynchronous scanning for FC/SAS version 3 Matthew Wilcox
2006-11-15 13:55 ` James Smart
2006-11-20 19:21 ` Andrew Vasquez
2006-11-20 20:11   ` Matthew Wilcox
2006-11-22 16:19     ` Andrew Vasquez
2006-11-22 16:22       ` [PATCH 1/2] Defer topology discovery to DPC thread during initialization Andrew Vasquez
2006-11-22 16:24         ` [PATCH 2/2] Add asynchronous scsi scanning support Andrew Vasquez
2006-11-22 17:51       ` Matthew Wilcox [this message]
2006-11-22 19:19         ` [RFC] Asynchronous scanning for FC/SAS version 3 Andrew Vasquez

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=20061122175125.GW18567@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=andrew.vasquez@qlogic.com \
    --cc=james.smart@emulex.com \
    --cc=linux-driver@qlogic.com \
    --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.