All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Malicki <jmalicki@metacarta.com>
To: Greg Dickie <greg@max-t.com>
Cc: "Brett G. Durrett" <brett@imvu.com>,
	linux-scsi@vger.kernel.org, linux-poweredge@dell.com,
	"David N. Welton" <d.welton@webster.it>,
	Sumant Patro <Sumant.Patro@lsil.com>,
	"Marc A. Meadows" <mam+megaraid@metacarta.com>,
	"Keith R. Baker" <krbaker+megaraid@metacarta.com>
Subject: Re: megaraid_sas waiting for command and then offline
Date: Tue, 12 Dec 2006 13:40:28 -0500	[thread overview]
Message-ID: <457EF79C.9030009@metacarta.com> (raw)
In-Reply-To: <1165926657.4991.132.camel@edinburgh.max-t.internal>

Thanks Greg,

Is there documentation or tests of the number of commands per LUN that
the hardware can handle?  The driver is clearly reading the value out of
a register on the card.

thanks,
joe

Greg Dickie wrote:
> We've never had lockups like this but we did notice that the
> megaraid_sas modules defaults to a much higher commands per lun setting
> than the hardware seems to be able to handle. IIRC the default is 128
> and we lowered it to 16 for the 5i and 32 for the 5E.
> 
> HTH,
> Greg
> 
> 


  reply	other threads:[~2006-12-12 18:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  3:04 megaraid_sas waiting for command and then offline Joe Malicki
2006-12-12  5:24 ` Brett G. Durrett
2006-12-12  5:53   ` Joseph Malicki
2006-12-12 12:30     ` Greg Dickie
2006-12-12 18:40       ` Joe Malicki [this message]
2006-12-20  1:03     ` Brett G. Durrett
  -- strict thread matches above, loose matches on Subject: below --
2006-10-25  8:46 David N. Welton
2006-10-25 22:48 ` Brett G. Durrett
2006-10-25 23:03   ` Alan Cox
2006-11-13 21:40   ` Brett G. Durrett
2006-09-06 17:14 Patro, Sumant
2006-09-06 20:44 ` Brett G. Durrett
2006-09-06  4:49 Brett G. Durrett
2006-09-06 14:11 ` Dave Lloyd
2006-09-06 16:04   ` Brett G. Durrett

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=457EF79C.9030009@metacarta.com \
    --to=jmalicki@metacarta.com \
    --cc=Sumant.Patro@lsil.com \
    --cc=brett@imvu.com \
    --cc=d.welton@webster.it \
    --cc=greg@max-t.com \
    --cc=krbaker+megaraid@metacarta.com \
    --cc=linux-poweredge@dell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mam+megaraid@metacarta.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 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.