public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Xiangliang Yu <yuxiangl@marvell.com>
Cc: "yxlraid@gmail.com" <yxlraid@gmail.com>,
	"jack_wang@usish.com" <jack_wang@usish.com>,
	"lucas.demarchi@profusion.mobi" <lucas.demarchi@profusion.mobi>,
	"maciej.trela@intel.com" <maciej.trela@intel.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jacky Feng <jfeng@marvell.com>
Subject: RE: [PATCH] [SCSI] LIBSAS: fix libsas link error issue
Date: Wed, 15 Jun 2011 01:57:30 -0400	[thread overview]
Message-ID: <1308117450.2329.31.camel@mulgrave> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19FAE669AF@SC-VEXCH4.marvell.com>

On Tue, 2011-06-14 at 18:44 -0700, Xiangliang Yu wrote:
> Subject: Re: [PATCH] [SCSI] LIBSAS: fix libsas link error issue
> 
> On Tue, 2011-06-14 at 23:17 +0800, yxlraid@gmail.com wrote:
> >> From: Xiangliang Yu <yuxiangl@marvell.com>
> >> 
> >> -- The value of child link rate should is minimum of link rate, or
> >>    command will fail if child link rate is bigger than parent link rate.
> >> 
> >> Signed-off-by: Xiangliang Yu <yuxiangl@marvell.com>
> >> ---
> >>  drivers/scsi/libsas/sas_expander.c |    2 +-
> >>  1 files changed, 1 insertions(+), 1 deletions(-)
> >> 
> >> diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c
> >> index 874e29d..6ccca09 100644
> >> --- a/drivers/scsi/libsas/sas_expander.c
> >> +++ b/drivers/scsi/libsas/sas_expander.c
> >> @@ -638,7 +638,7 @@ static void sas_ex_get_linkrate(struct domain_device *parent,
> >>  			sas_port_add_phy(port, phy->phy);
> >>  		}
> >>  	}
> >> -	child->linkrate = min(parent_phy->linkrate, child->max_linkrate);
> >> +	child->linkrate = min(parent_phy->linkrate, child->min_linkrate);
> 
> >This patch doesn't look right.  It will clamp the phy to the minim
> >possible link rate.  
> Link negotiation should get the minimum.

No ... according to the spec it should be the max of what the child
supports taking into account the max the expander phy supports.

> >The child is supposed to support everywhere between
> >child->min_linkrate and child->max_linkrate.  The reason why we pick the
> >max is because we should use that if the parent supports it, and fall
> >back only if the parent isn't capable.
> Now, the problem is command fail, and LIBSAS seem to do nothing.
> Do you mean drive need to fix the link error?
> Thanks!
> 
> PS: The Kernel will panic when link error happening.

Post the panic then ... it's probably a negotiation problem.  If the
child can't support the highest possible link rate because of problems
like transmission errors, it should fall back.

James



  parent reply	other threads:[~2011-06-15  5:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 15:17 [PATCH] [SCSI] LIBSAS: fix libsas link error issue yxlraid
2011-06-14 15:29 ` James Bottomley
2011-06-15  1:44   ` Xiangliang Yu
2011-06-15  4:15     ` Douglas Gilbert
2011-06-15  4:52       ` Xiangliang Yu
2011-06-15  5:57     ` James Bottomley [this message]
2011-06-15  6:31       ` Xiangliang Yu
2011-06-16  1:41         ` Jack Wang
2011-06-16  1:57           ` Xiangliang Yu
2011-06-16  2:18             ` Jack Wang
2011-06-16  2:29               ` Xiangliang Yu
2011-06-16  4:31                 ` Jack Wang
2011-06-16  4:53                   ` Xiangliang Yu
2011-06-16  6:12                     ` Jack Wang
2011-06-16  6:37                       ` Xiangliang Yu
2011-06-16  6:55                         ` Jack Wang
2011-06-16  7:27                           ` Xiangliang Yu
2011-06-16  8:11                             ` Jack Wang
2011-06-16  9:04                               ` Xiangliang Yu
2011-06-16  9:33                                 ` Jack Wang

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=1308117450.2329.31.camel@mulgrave \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dan.j.williams@intel.com \
    --cc=jack_wang@usish.com \
    --cc=jfeng@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=maciej.trela@intel.com \
    --cc=yuxiangl@marvell.com \
    --cc=yxlraid@gmail.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