[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <504F7906.9040806@intel.com>
Date: Tue, 11 Sep 2012 17:46:47 +0000
From: "Love, Robert W" <robert.w.love@...el.com>
To: Chris Leech <leech@...ox.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devel@...n-fcoe.org" <devel@...n-fcoe.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: Re: [Open-FCoE] [RFC PATCH 0/5] Reorganize libfcoe control
interfaces
On Tue 11 Sep 2012 10:36:35 AM PDT, Love, Robert W wrote:
> On Tue 11 Sep 2012 10:06:29 AM PDT, Chris Leech wrote:
>> On Mon, Sep 10, 2012 at 3:59 PM, Robert Love <robert.w.love@...el.com> wrote:
<snip>
>> That being said, I'm glad this is being reworked. Do you have any
>> other functionality in mind that this is laying the groundwork for?
>>
>
> I have one feature and a few ideas. I currently have a patch that adds
> a fabric selection feature. I add another RW attribute to the ctlr_X
> device. If the user writes fabric name to the file libfcoe uses it in
> it's FCF selection algorithm. Here's my commit message from that patch.
> I can share the patch if people would like to see it too. The current
> implementation also allows the user to force the login through a
> specific FCF.
>
My fcoe-utils.git change here also allows the user to drive this fabric
selection using a new variable in the /etc/fcoe/cfg-ethX files that the
'fcoe service' uses.
Powered by blists - more mailing lists