From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sreekanth Reddy <sreekanth.reddy@avagotech.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Hannes Reinecke <hare@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Sathya Prakash <Sathya.Prakash@avagotech.com>,
Nagalakshmi Nandigama <Nagalakshmi.Nandigama@avagotech.com>,
linux-scsi@vger.kernel.org
Subject: Re: mpt2sas and mpt3sas merge (again)
Date: Tue, 22 Jul 2014 21:39:08 -0400 [thread overview]
Message-ID: <yq14my8lupv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAK=zhgoD9vVH0zCORTA2Mhu8Tf4m4VAih_hpig4PDdh-vgJmQg@mail.gmail.com> (Sreekanth Reddy's message of "Tue, 22 Jul 2014 12:03:48 +0530")
>>>>> "Sreekanth" == Sreekanth Reddy <sreekanth.reddy@avagotech.com> writes:
Hey Sreekanth,
Sreekanth> If we have single driver approach, making any changes in
Sreekanth> driver require lots of regression and Q/A cycle so that
Sreekanth> existing customer who are based on older controller does not
Sreekanth> have any impact due some fixes/new features.
Sreekanth> With all these HBA specific features, it is unmanageable to
Sreekanth> have a common driver for SAS2 and SAS3 HBAs.
But just as a counterexample to that: qla2xxx and lpfc are both capable
of driving a wide range of chip generations and firmware interface
versions with a single driver.
The problem I have with the mpt2sas/mpt3sas split is that there are way
more commonalities than there are differences. It is trivial to handle
multiple scatterlist format and features in a single driver. You guys
already do that in megaraid_sas.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-07-23 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 8:35 mpt2sas and mpt3sas merge (again) Christoph Hellwig
2014-07-14 9:22 ` Hannes Reinecke
2014-07-14 14:17 ` James Bottomley
2014-07-14 14:39 ` Hannes Reinecke
2014-07-14 14:57 ` James Bottomley
2014-07-14 15:10 ` Hannes Reinecke
2014-07-14 17:00 ` Tomas Henzl
2014-07-14 21:34 ` Martin K. Petersen
[not found] ` <CAK=zhgoD9vVH0zCORTA2Mhu8Tf4m4VAih_hpig4PDdh-vgJmQg@mail.gmail.com>
2014-07-23 1:39 ` Martin K. Petersen [this message]
2014-07-24 12:25 ` Sreekanth Reddy
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=yq14my8lupv.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Nagalakshmi.Nandigama@avagotech.com \
--cc=Sathya.Prakash@avagotech.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sreekanth.reddy@avagotech.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