linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Chris Boot <bootc@boo.tc>,
	linuxppc-dev@lists.ozlabs.org, target-devel@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Chuhong Yuan <hslester96@gmail.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: [PATCH] scsi: target/sbp: remove firewire SBP target driver
Date: Mon, 4 Jan 2021 17:48:06 -0800	[thread overview]
Message-ID: <9103b316-8848-2350-7c0d-b742c8d8c83c@acm.org> (raw)
In-Reply-To: <alpine.LNX.2.23.453.2101050840010.6@nippy.intranet>

On 1/4/21 2:50 PM, Finn Thain wrote:
> On Mon, 4 Jan 2021, Bart Van Assche wrote:
>> Additionally, there is a good alternative available for the sbp driver. 
>> Every system I know of that is equipped with a Firewire port also has an 
>> Ethernet port. So users who want to provide SCSI target functionality on 
>> such systems can use any SCSI transport protocol that is compatible with 
>> Ethernet (iSCSI, iSER over soft-RoCE, SRP over soft-RoCE, ...).
> 
> Ethernet is not always an alternative. That was already discussed in this 
> thread. But let's assume for a moment that you can migrate any and all 
> users of this driver over to an ethernet driver.
> 
> Why would the maintainers of that Ethernet driver and its API accept that 
> plan, if adding users would extend their maintenance and testing 
> obligations? Do you think those maintainers should pay the "kind of tax 
> that all developers/users pay to all developers/users?"

Hi Finn,

I cannot speak in the name of the iSCSI over TCP/IP or iSER driver
maintainers. But since I maintain the SRP initiator and target kernel
drivers myself, I can state that I would be happy to help SBP target users
(if that driver has any users today) to switch from SCSI over Firewire to
SCSI over SRP over RoCE or even NVMEoF over TCP.

Thanks,

Bart.

  reply	other threads:[~2021-01-05  1:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13  8:37 [PATCH] scsi: target/sbp: remove SBP target driver Chris Boot
2020-06-14  0:03 ` [PATCH] scsi: target/sbp: remove firewire " Finn Thain
2020-06-14 10:34   ` Chris Boot
2020-06-14 23:28     ` Finn Thain
2020-06-15 15:00       ` Chris Boot
2020-06-16  9:42         ` Finn Thain
2020-06-16 14:08           ` Bart Van Assche
2020-06-16 14:13             ` Johannes Thumshirn
2020-06-16 15:34               ` James Bottomley
2020-06-16 17:59                 ` Chris Boot
2020-06-17  3:09                   ` Martin K. Petersen
2020-06-18  0:40                     ` Finn Thain
2020-06-17  2:07             ` Finn Thain
2021-01-04 17:43               ` Bart Van Assche
2021-01-04 22:50                 ` Finn Thain
2021-01-05  1:48                   ` Bart Van Assche [this message]
2020-06-17  2:35   ` Martin K. Petersen
2020-06-17  4:21     ` Finn Thain

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=9103b316-8848-2350-7c0d-b742c8d8c83c@acm.org \
    --to=bvanassche@acm.org \
    --cc=bootc@boo.tc \
    --cc=fthain@telegraphics.com.au \
    --cc=hslester96@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=target-devel@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 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).