From: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
Christian Svensson <christian-IHD7e6/dsE0@public.gmane.org>,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: fcoe-devel-s9riP+hp16TNLxjTenLetw@public.gmane.org
Subject: Re: FICON target support
Date: Fri, 31 May 2019 08:06:29 +0200 [thread overview]
Message-ID: <69308786-81d8-a9df-2d7b-df37c3f93026@suse.de> (raw)
In-Reply-To: <5c5609d8-e4b4-3561-ece9-93746fd46206-HInyCGIudOg@public.gmane.org>
On 5/31/19 1:10 AM, Bart Van Assche wrote:
> On 5/26/19 8:51 AM, Christian Svensson wrote:
>> I am doing some preliminary scouting of how one could add support for
>> FICON (FC-SB-3 specifically). I am mostly interested in Linux being
>> able to act as a FICON target for now.
>>
>> The TL;DR summary for FICON is that it uses Fibre Channel just like
>> FCP/SCSI
>> up to but not including the FC-4 (FCP) layer. At that point it uses
>> its own SBCCS layer.
>>
>> FICON is used by IBM mainframes to interface peripherals like tape, disk,
>> printers, card punchers/readers, etc. It is more like a mainframe
>> USB/Firewire than SCSI in that regard.
>>
>> I would prefer to implement my peripherals in user-space, I don't see any
>> convincing case for having e.g. a virtual tape drive running in kernel
>> space.
>> The I/O heavy disks would probably benefit from being in kernel space,
>> but I am OK limiting the initial scope.
>>
>> I am 100% new to the SCSI and Fibre Channel subsystem in Linux, and I
>> do not even know if the current HBAs support sending frames without FCP
>> but after scouting the code it does seem that it might work out - FCP
>> seems decoupled enough.
>>
>> If you want to learn more the standard document Wireshark has an
>> implementation of the protocol (packet-fcsb3.c/h). If you want all the
>> details
>> you will sadly have to pay $60 and buy it from INCITS at
>> https://webstore.ansi.org/Standards/INCITS/INCITS3742003S2013.
>> Fwiw, FICON uses FC type 0x1B and 0x1C.
>>
>> Any thoughts or ideas where you would start? Do you see any future for
>> this addition to the kernel?
>
> Hi Chris,
>
> I'm not sure what the best approach is for the initiator functionality.
> For the target functionality you may want to have a look at tcmu
> (Documentation/target/tcmu-design.txt and
> drivers/target/target_core_user.c). An existing FC target driver is
> available in drivers/scsi/qla2xxx/tcm_qla2xxx.c. A diagram that shows
> the different functional blocks in TCM is available at
> https://en.wikipedia.org/wiki/LIO_(SCSI_target) (LIO is another name for
> TCM).
>
Hmm. I wonder: do you _know_ what you are asking?
Have you ever worked with a mainframe?
Thing is, from an initiator side you don't even _see_ the FICON frames;
everything is abstracted away to some higher level.
IE you have no idea how the initiator formats frames and what it expects
in return. Which makes debugging pretty much impossible unless you're
having access to a fibrechannel analyser hooked up to a mainframe.
Hmm?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
_______________________________________________
fcoe-devel mailing list
fcoe-devel@open-fcoe.org
http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel
next prev parent reply other threads:[~2019-05-31 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADiuDASOCJbnwLs-LEp0aCX+T4dMvFfKQv_zsypHW-iSF8wW=Q@mail.gmail.com>
2019-05-30 23:10 ` FICON target support Bart Van Assche
[not found] ` <5c5609d8-e4b4-3561-ece9-93746fd46206-HInyCGIudOg@public.gmane.org>
2019-05-31 6:06 ` Hannes Reinecke [this message]
[not found] ` <CADiuDATRN_85Tu3uw1WBtY=m8KrqKV5zpYrsggYdAOH23dwU=Q@mail.gmail.com>
2019-05-31 8:08 ` Hannes Reinecke
[not found] ` <CADiuDARPit+kKtQe-UGktUuxEXRMvoq7PGVPKo9DrLRkSTwNAA@mail.gmail.com>
[not found] ` <CADiuDARPit+kKtQe-UGktUuxEXRMvoq7PGVPKo9DrLRkSTwNAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-05-31 10:17 ` Hannes Reinecke
[not found] ` <CADiuDASfjq=xyuTEF2VZtb+dV78_VdMRkfFrr4ujs0zPXjv7Ew@mail.gmail.com>
2019-10-03 16:38 ` [Open-FCoE] " Christian Svensson
2019-10-03 18:37 ` Laurence Oberman
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=69308786-81d8-a9df-2d7b-df37c3f93026@suse.de \
--to=hare-l3a5bk7wagm@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=christian-IHD7e6/dsE0@public.gmane.org \
--cc=fcoe-devel-s9riP+hp16TNLxjTenLetw@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).