Linux SCSI subsystem development
 help / color / mirror / Atom feed
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 10:08:06 +0200	[thread overview]
Message-ID: <9612602b-29c0-04d7-b76e-5593d0936eba@suse.de> (raw)
In-Reply-To: <CADiuDATRN_85Tu3uw1WBtY=m8KrqKV5zpYrsggYdAOH23dwU=Q@mail.gmail.com>

On 5/31/19 9:13 AM, Christian Svensson wrote:
> Hi Hannes,
> 
> On Fri, May 31, 2019 at 8:06 AM Hannes Reinecke <hare@suse.de> wrote:
>> Hmm. I wonder: do you _know_ what you are asking?
>> Have you ever worked with a mainframe?
> 
> I can assure you I have no idea what I am doing :-). I am doing this as a
> learning project where my aim is to implement a virtual card reader in
> user space.
> 
There are easier ways for this ... I'd start with virtio-ccw and
implement a virtual PUNCHER there ...

>>  unless you're having access to a fibrechannel analyser hooked up to a mainframe.
> 
> Funnily enough, I happen to own both.
> 
Oh. Now _that_ is unexpected.
Then I would not stand in your way.

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 ...)

However, I do wonder how you came by an FC analyser ... any chance of me
borrowing it occasionally?

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

  parent reply	other threads:[~2019-05-31  8:08 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 [this message]
     [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=9612602b-29c0-04d7-b76e-5593d0936eba@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