public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] lpfc : add module parameter that allows adapter	instances to avoid attachment
Date: Thu, 26 Mar 2009 15:54:09 -0500	[thread overview]
Message-ID: <1238100849.3342.58.camel@localhost.localdomain> (raw)
In-Reply-To: <49CBE772.80304@emulex.com>

On Thu, 2009-03-26 at 16:37 -0400, James Smart wrote:
> The oem requirement we have explicitly states not to use the unbind interface
> (we proposed unbind at first as well).
> 
> The issue is what happens on the link while we are bound for that short
> amount of time. It confuses the things on the other side of the link.
> There's a secondary driver that ends up binding to the adapters we exclude,
> and the things on the other side only expected to see the second driver.

OK, so it sounds like a proposed extension to the generic unbind
interfaces where you specify a no_bind list on the kernel or module
command line.

Also (as Randy pointed out) you don't account for the domain.  However,
you could just by not bothering to convert the string to numbers for the
compare, just compare on dev->bus_id ... which is how a generic one
would work.

James



  parent reply	other threads:[~2009-03-26 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 19:55 [PATCH] lpfc : add module parameter that allows adapter instances to avoid attachment James Smart
2009-03-26 20:19 ` James Bottomley
2009-03-26 20:37   ` James Smart
2009-03-26 20:41     ` Randy Dunlap
2009-03-26 20:54     ` James Bottomley [this message]
2009-03-27 12:46       ` James Smart
2009-03-27 15:09       ` Matthew Wilcox
2009-03-27 15:33         ` James Bottomley
2009-03-27 16:14           ` Matthew Wilcox
2009-03-27 16:41             ` James Bottomley
2009-03-27 15:11     ` Matthew Wilcox
2009-03-26 20:43 ` Matthew Wilcox

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=1238100849.3342.58.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=James.Smart@Emulex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox