From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"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 13:41:15 -0700 [thread overview]
Message-ID: <49CBE86B.4050701@oracle.com> (raw)
In-Reply-To: <49CBE772.80304@emulex.com>
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.
>
> -- james s
>
>
> James Bottomley wrote:
>> On Thu, 2009-03-26 at 15:55 -0400, James Smart wrote:
>>> This patch adds a module parameter that supplies a text string
>>> containing a
>>> list of PCI <bus>:<slot>.<func> values to identify adapter instances
>>> that
>>> should *not* be attached to by the driver.
What does this do on systems that use PCI domains?
domain:bus:slot.func (??)
>>> -- james s
>>>
>>>
>>> Signed-off-by: James Smart <james.smart@emulex.com>
>>
>> Is there a reason why you can't just use the generic unbind interface?
>>
>> James
--
~Randy
next prev parent reply other threads:[~2009-03-26 20:41 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 [this message]
2009-03-26 20:54 ` James Bottomley
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=49CBE86B.4050701@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=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