All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: adam radford <aradford@gmail.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Bo.Yang@lsi.com
Subject: Re: [PATCH 0/10] megaraid_sas: Updates for scsi-misc
Date: Sun, 09 Oct 2011 20:56:59 -0400	[thread overview]
Message-ID: <4E9242DB.7040401@interlog.com> (raw)
In-Reply-To: <1318169420.2998.6.camel@dabdike.int.hansenpartnership.com>

On 11-10-09 10:10 AM, James Bottomley wrote:
> On Sun, 2011-10-09 at 09:56 -0400, Douglas Gilbert wrote:
>> On 11-10-08 09:14 PM, adam radford wrote:
>>> James/Linux-scsi,
>>>
>>> The following patch series for megaraid_sas brings the driver up to v6.12-rc1:
>>>
>>> 1. Continue booting immediately if FW in FAULT at driver load time.
>>> 2. Increase default cmds per lun to 256.
>>> 3. Fix mismatch in megasas_reset_fusion() mutex lock-unlock.
>>> 4. Remove some un-necessary code.
>>> 5. Clear state change interrupts for Fusion/Invader.
>>> 6. Clear FUSION_IN_RESET before enabling interrupts.
>>> 7. Add support for MegaRAID 9360/9380 12GB/s controllers.
>>> 8. Add multiple MSI-X vector/multiple reply queue support.
>>> 9. Add driver workaround for PERC5/1068 kdump kernel panic.
>>> 10. Version and Changelog update.
>>
>> I haven't checked all SAS HBAs in Linux but of those that I
>> have checked only one doesn't support the SMP pass-through
>> in the bsg driver. And that HBA driver is megaraid_sas **.
>
> Technically the megaraid_sas isn't really a SAS HBA, it's a RAID one
> that just happens to have SAS/SATA disk attachments.  None of the RAID
> HBA's (including the IBM power raid) expose a BSG interface or even
> attach properly to the in-kernel SAS interfaces.

In JBOD mode MegaRaid SAS controllers are SAS HBAs
(marketing BS aside). Their firmware has the same
SMP pass-through as LSI's MPT SAS Fusion controllers.

There is no reason why a MegaRaid controller user
couldn't place a SAS-2 expander in front of an array
of disks and make some disks available to a MegaRaid
volume. Other array disks could be used by other
machines and the different sets could be isolated
from each other with SAS-2 zoning. The problem then
would be that via a MegaRaid SAS controller a user
could not monitor or control that zoning. Seems a
bit wasteful to add a "real" SAS HBA just to get
that capability.

Many SAS HBAs (including MPT SAS Fusion controllers)
do RAID 0 and 1 (and 10?) so they could be viewed as
"RAID" controllers that expose a BSG interface.

Doug Gilbert




  reply	other threads:[~2011-10-10  0:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  1:14 [PATCH 0/10] megaraid_sas: Updates for scsi-misc adam radford
2011-10-09 13:56 ` Douglas Gilbert
2011-10-09 14:10   ` James Bottomley
2011-10-10  0:56     ` Douglas Gilbert [this message]
2011-10-10  7:02       ` Hannes Reinecke
2011-10-12  7:31         ` Hannes Reinecke
2011-10-10 14:07       ` James Bottomley

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=4E9242DB.7040401@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=Bo.Yang@lsi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aradford@gmail.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 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.