From: Laurence Oberman <loberman@redhat.com>
To: Christian Svensson <christian@cmd.nu>, Hannes Reinecke <hare@suse.de>
Cc: Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org, fcoe-devel@open-fcoe.org
Subject: Re: [Open-FCoE] FICON target support
Date: Thu, 03 Oct 2019 14:37:22 -0400 [thread overview]
Message-ID: <7928c78bb3e7c7a37b6b75683233bad841c43d9b.camel@redhat.com> (raw)
In-Reply-To: <CADiuDASkpY_2HD4rfc2hxDOQPkbxKpgVv1EeSS60ZZhwqag_2w@mail.gmail.com>
On Thu, 2019-10-03 at 18:38 +0200, Christian Svensson wrote:
> Hi,
>
> An update if you're curious about this. I found that DE5-Net FPGA
> cards are reasonably priced right now on eBay, so I started a project
> to implement FICON target support. You can find more information on
> github: https://github.com/bluecmd/fejkon
>
> Essentially it's a 4x SFP+ port card for $300-$400 that I will export
> as "fc0-3" netdev's using ARPHRD_FCFABRIC type.
> This allows libpcap to capture raw FC directly on the netdev. The
> devices will be fully TX/RX capable.
>
> FICON and normal FCP will be implemented in userspace by reading /
> writing packets straight to the netdev.
> I assume this will be CPU intensive but for my purposes it should be
> fine. Maybe it is a good solution for people that want a more modern
> Fibre Channel analyzer as well.
>
> Regards,
> Christian
Very interesting and thanks for sharing
Regards
Laurence
prev parent reply other threads:[~2019-10-03 18:37 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
[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 [this message]
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=7928c78bb3e7c7a37b6b75683233bad841c43d9b.camel@redhat.com \
--to=loberman@redhat.com \
--cc=bvanassche@acm.org \
--cc=christian@cmd.nu \
--cc=fcoe-devel@open-fcoe.org \
--cc=hare@suse.de \
--cc=linux-scsi@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).