From: Garrett D'Amore <garrett@damore.org>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] Broadcom 3816/3808 SAS controller, 16/8 internal ports, 12Gb/s per port
Date: Thu, 7 Jul 2022 14:31:21 +0000 [thread overview]
Message-ID: <BYAPR05MB6248FDEB030A106E7315DDB6AE839@BYAPR05MB6248.namprd05.prod.outlook.com> (raw)
In-Reply-To: <58E65E73-8195-4FFD-B9F8-F3C209DE3110@mnx.io>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Any of those are good choices. Smrt is probably the best because it has support for SMP and both physical and logical LUNs. So closest to the needs of real hardware I think.
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Dan McDonald <danmcd@mnx.io>
Sent: Thursday, July 7, 2022 7:19:33 AM
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] Broadcom 3816/3808 SAS controller, 16/8 internal ports, 12Gb/s per port
On Jul 7, 2022, at 10:06 AM, Garrett D'Amore <garrett@damore.org> wrote:
>
> Honestly, rather than extending mpt_sas or mr_sas, I wish that someone would just make a new driver, and make it use iport() and tran_setup_pkt(). The driver would be smaller and hopefully a lot easier to maintain. There is a small chance that I might even do this myself, but it is just a matter of having enough time to do it, combined with no pressing need for it at RackTop right now.
>
Which driver that uses iport() & tran_setup_pkt() would be a good reference? Looks like we have pmcs, smrt, and vioscsi to pick from.
Dan
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Tc07685e55bd13e0d-Mcc4d55bf14eeb4bbd387d25e
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
[-- Attachment #2: Type: text/html, Size: 2244 bytes --]
next prev parent reply other threads:[~2022-07-07 14:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 8:30 Gabriele Bulfon
2021-10-25 13:29 ` kilian.ries
2021-10-25 14:26 ` [developer] " Robert Mustacchi
2021-10-25 14:57 ` Gabriele Bulfon
2021-10-25 15:06 ` [developer] " InterNetX - Kilian Ries
2021-10-25 15:34 ` Marcel Telka
2021-10-26 8:47 ` Marcel Telka
2021-10-30 14:55 ` Robert Mustacchi
2021-11-02 9:44 ` Marcel Telka
2021-12-01 16:27 ` InterNetX - Kilian Ries
2021-12-16 14:39 ` Marcel Telka
2021-10-25 15:40 ` Robert Mustacchi
2021-10-25 15:48 ` InterNetX - Kilian Ries
2022-04-30 10:39 ` clement.jourdan
2022-05-02 23:37 ` smaybee
2022-07-07 13:11 ` kilian.ries
2022-07-07 13:51 ` Schweiss, Chip
2022-07-07 14:06 ` Garrett D'Amore
2022-07-07 14:19 ` Dan McDonald
2022-07-07 14:31 ` Garrett D'Amore [this message]
2022-07-07 21:13 ` Stuart Maybee
2022-07-07 21:19 ` Joshua M. Clulow
2022-12-02 8:40 ` Tobias Oetiker
2022-12-09 12:00 ` Carsten Grzemba
2023-05-01 20:59 ` smaybee
2023-05-01 21:01 ` Dan McDonald
2023-05-01 21:32 ` Stuart Maybee
2023-05-01 21:46 ` Stuart Maybee
2023-10-06 16:10 ` Dan McDonald
2023-10-06 18:40 ` Dan McDonald
2023-10-15 15:33 ` gearboxes
2023-10-16 7:29 ` Stuart Maybee
2023-10-16 15:21 ` Dan McDonald
2023-10-16 23:29 ` gearboxes
2023-10-19 18:40 ` Dan McDonald
2023-10-19 20:11 ` Stuart Maybee
2024-03-20 0:36 ` mike.aldred
2024-03-20 13:01 ` Dan McDonald
2024-03-20 14:34 ` Mike Aldred
2024-03-23 4:56 ` Dan McDonald
2023-05-01 20:53 ` smaybee
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=BYAPR05MB6248FDEB030A106E7315DDB6AE839@BYAPR05MB6248.namprd05.prod.outlook.com \
--to=garrett@damore.org \
--cc=developer@lists.illumos.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;
as well as URLs for NNTP newsgroup(s).