mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Scott Edwards" <lkml@foss.daxal.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Fibre channel network interfaces + Linux SAN
Date: Mon, 17 Mar 2008 09:18:36 -0500	[thread overview]
Message-ID: <20080317141836.29FB5320007@mail.daxal.com> (raw)

Two things I'm trying to solve with my fc hardware.  How do I enable these 
for IP networking, and how do I offer say lvm logical volumes behind Linux 
as a SAN? I'd like nodes to be bootable and offer specific volumes as their 
disks.  I'm using 2.6.28 

As for networking, I vaguely remember setting up IPv4 on fibre channel some 
time ago.  So far I have two hosts connected to a Compaq Storage Works FC 
arbitrated loop.  Each host has Online for 
/sys/class/fc_host/hostN/port_state.  I can't find the network device in 
/proc/net/dev or via ifconfig -a. 

riddle: 2.6.18-5-xen-vserver-686
00:0a.0 Fibre Channel [0c04]: Emulex Corporation LP8000 Fibre Channel Host 
Adapter [10df:f800] (rev 02) 

armada: 2.6.18-5-vserver-686
01:0b.0 Fibre Channel [0c04]: Emulex Corporation LP8000 Fibre Channel Host 
Adapter [10df:f800] (rev 02) 

Both have lpfc loaded (if you didn't guess that by now).  I thought there 
was a more generic ip<->fc net driver. I did find net/802/fc.c using fc%d as 
the net device, and lpfc.ko is the only module I've found containing fc%d. 

modinfo lpfc seems to apply to the fc layer only.  I did find some outdated 
Emulex documentation about configuring this hardware for a network 
interface. 

Any comments? 

Thanks, 


Scott
 -- Daxal Communications - http://sslrenewal.com/?lkml 


             reply	other threads:[~2008-03-17 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 14:18 Scott Edwards [this message]
     [not found] <47E01DB3.90307@emulex.com>
2008-03-18 21:16 ` James Smart

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=20080317141836.29FB5320007@mail.daxal.com \
    --to=lkml@foss.daxal.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®