From: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
To: Christian Svensson <christian-IHD7e6/dsE0@public.gmane.org>
Cc: fcoe-devel-s9riP+hp16TNLxjTenLetw@public.gmane.org,
Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: FICON target support
Date: Fri, 31 May 2019 12:17:47 +0200 [thread overview]
Message-ID: <17f0639d-bd44-c193-af29-df539be722fe@suse.de> (raw)
In-Reply-To: <CADiuDARPit+kKtQe-UGktUuxEXRMvoq7PGVPKo9DrLRkSTwNAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 5/31/19 10:52 AM, Christian Svensson wrote:
> Hi,
>
> On Fri, May 31, 2019 at 10:08 AM Hannes Reinecke <hare@suse.de> wrote:
>> There are easier ways for this ... I'd start with virtio-ccw and
>> implement a virtual PUNCHER there ...
>
> The larger project scope is making FICON accessories more available
> for people as crazy as I, that is wanting to run a mainframe as a
> hobbyist, but maybe not want to buy a metric ton worth of disks or
> tape robots (a 700 kg mainframe is hard enough by itself to house).
>
> I will take a look, but from the name of it it sounds like it will not
> help me much getting FICON targets supported.
> Maybe it will help if I ever want FICON initiator.
>
Right.
>> Still, an uphill struggle; IBM is notorious for not giving out details
>> about the internals, and simulating a puncher is one of these things.
>> (And slightly pointless, but who am I to judge ...)
>
> It's a low-speed peripheral that has been emulated successfully in
> Hercules, and there are some petty detailed documents around the CCWs
> for 3505 around. I figured it would
> be a good start getting a FICON user-space thing implemented, before I
> try to tackle e.g. ECKDs or tapes.
>
Oh. Sure. You might want to ask on the s390 mailing lists, too; they
typically have a quite good idea on what's going on.
The biggest problem, however, will be to get the documentation from the
HBAs themselves.
All FC HBAs will present you with some version of cooked frames, and not
allow you to access the frames themselves. So in the end you'd have to
see to get hold of the HBA documentation itself, as you need to figure
out how to pass FICON frames into the HBA.
It might be easier when you'd be working with FCoE cards, as there you
_do_ have access to the full frame, and do whatever you like with thems.
Sadly you'd need an FCoE bridge then to hook up the mainframe.
But as you have gotten hold of an FC analyser, getting an FCoE bridge
shouldn't be too hard, too :-)
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 10:17 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
[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 [this message]
[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=17f0639d-bd44-c193-af29-df539be722fe@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