From: "Jack Wang" <jack_wang@usish.com>
To: 'Dan Williams' <dan.j.williams@intel.com>
Cc: james.bottomley@suse.de,
'Jeff Skirvin' <jeffrey.d.skirvin@intel.com>,
'Patrick Thomson' <patrick.s.thomson@intel.com>,
linux-scsi@vger.kernel.org
Subject: RE: [PATCH] libsas: fix definition of wideport, include local sas address
Date: Mon, 4 Oct 2010 07:47:08 +0800 [thread overview]
Message-ID: <803C0CAF9ECC49B1B53C41064DE42DF0@usish.com.cn> (raw)
In-Reply-To: <AANLkTi=rM=7r6tnxCrc42q=e6r0U2LKPyoUa-D5j3MKa@mail.gmail.com>
Re: [PATCH] libsas: fix definition of wideport, include local sas address
On Sat, Oct 2, 2010 at 6:55 PM, Jack Wang <jack_wang@usish.com> wrote:
>
> To date libsas has only looked at the attached sas address when
> determining the formation of wide ports. The specification and some
> hardware expects that phys with different addresses will not form a wide
> port unless the local peer phys also match each other. Introduce a flag
> to select stricter behavior at sas_register_ha() time. The flag can be
> dropped once it is known that all libsas users expect the same behavior.
>
> Current drivers just initialize this field to zero and get the
> traditional behavior.
> [Jack] I prefer to use the new definition of wideport to the default.
Ok, when mvsas and aic94xx are also ready for this change we can just
make this the default and kill the flag.
> [Jack] I cann't find where to judge the flag to chose which definition to
> use?
I am not clear on the question. phy_is_wideport_member() should be
the only location that needs to read this flag. The driver just sets
it to 1 before calling sas_register_ha() and then assumes the strict
definition is in effect for the lifetime of the driver instance.
[Jack] Ohh, I miss something in the patch. It's ok for me. Thanks for
Explanation.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-10-05 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 20:55 [PATCH] libsas: fix definition of wideport, include local sas address Dan Williams
2010-10-03 1:55 ` Jack Wang
2010-10-04 16:44 ` Dan Williams
2010-10-03 23:47 ` Jack Wang [this message]
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=803C0CAF9ECC49B1B53C41064DE42DF0@usish.com.cn \
--to=jack_wang@usish.com \
--cc=dan.j.williams@intel.com \
--cc=james.bottomley@suse.de \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patrick.s.thomson@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox