<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/scsi/fcoe/libfcoe.c, branch linux-2.6.33.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.33.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.33.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-02-17T15:57:03Z</updated>
<entry>
<title>[SCSI] libfcoe: Send port LKA every FIP_VN_KA_PERIOD secs.</title>
<updated>2010-02-17T15:57:03Z</updated>
<author>
<name>Bhanu Prakash Gollapudi</name>
</author>
<published>2010-01-21T18:16:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f47dd855d9e64a5d499a93e858a82bc5e7b21345'/>
<id>urn:sha1:f47dd855d9e64a5d499a93e858a82bc5e7b21345</id>
<content type='text'>
libfcoe module doesnt send port keep alive every
FIP_VN_KA_PERIOD due to improper assignment of timeout value.
Update the port_ka_time appropriately by incrementing it by
FIP_VN_KA_PERIOD in fcoe_ctlr_timeout(), so that the link_work
is scheduled to send the port LKA.

Signed-off-by: Bhanu Gollapudi &lt;bprakash@broadcom.com&gt;
Acked-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: add tracking FIP Missing Discovery Advertisement count</title>
<updated>2009-12-04T18:01:56Z</updated>
<author>
<name>Yi Zou</name>
</author>
<published>2009-11-20T22:55:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f3da80e76142d63a6849556461906fbe118d1442'/>
<id>urn:sha1:f3da80e76142d63a6849556461906fbe118d1442</id>
<content type='text'>
Add tracking the Missing Discovery Advertisement count for FIP Fiber Channel
Forwarder (FCF) as described in FC-BB-5 Rev2.0 for LESB. The time is 1.5 times
the FKA_ADV_PERIOD of the corresponding FCF.

Signed-off-by: Yi Zou &lt;yi.zou@intel.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: add tracking FIP Virtual Link Failure count</title>
<updated>2009-12-04T18:01:56Z</updated>
<author>
<name>Yi Zou</name>
</author>
<published>2009-11-20T22:55:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2ec8493f962d55ae85c6716db414c645a6578333'/>
<id>urn:sha1:2ec8493f962d55ae85c6716db414c645a6578333</id>
<content type='text'>
Add tracking the Virtual Link Failure count when either we have found
the FCF as "aged" or we are receiving FIP Clear Virtual Link from the
FCF.

Signed-off-by: Yi Zou &lt;yi.zou@intel.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: add checking disable flag in FIP_FKA_ADV</title>
<updated>2009-12-04T18:01:55Z</updated>
<author>
<name>Yi Zou</name>
</author>
<published>2009-11-20T22:54:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8cdffdccd948ea4872b7b65280bc04f2fa93fc96'/>
<id>urn:sha1:8cdffdccd948ea4872b7b65280bc04f2fa93fc96</id>
<content type='text'>
When the D bit is set if the FKA_ADV_Period of the FIP Discovery
Advertisement, the ENode should not transmit period ENode FIP Keep Alive and
VN_Port FIP Keep Alive (FC-BB-5 Rev2, 7.8.3.13).

Note that fcf-&gt;flags is taken directly from the fip_header, I am claiming one
bit for the purpose of the FIP_FKA_Period D bit as FIP_FL_FK_ADV_B, and use
FIP_HEADER_FLAGS as bitmask for bits used in fip_header.

Signed-off-by: Yi Zou &lt;yi.zou@intel.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: Do not pad FIP keep-alive to full frame size</title>
<updated>2009-12-04T18:01:27Z</updated>
<author>
<name>Yi Zou</name>
</author>
<published>2009-11-03T19:50:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=be276cbe1bd680ab1f6c297017dd658e5a6b10d2'/>
<id>urn:sha1:be276cbe1bd680ab1f6c297017dd658e5a6b10d2</id>
<content type='text'>
According to the FC-BB-5 Rev2.0, 7.8.6.2, we should not pad FIP keep-alive
frames.

Signed-off-by: Yi Zou &lt;yi.zou@intel.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: fcoe: simplify receive FLOGI response</title>
<updated>2009-12-04T18:01:18Z</updated>
<author>
<name>Joe Eykholt</name>
</author>
<published>2009-11-03T19:49:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=386309ce927a308d7742a6fb24a536d3383fbd49'/>
<id>urn:sha1:386309ce927a308d7742a6fb24a536d3383fbd49</id>
<content type='text'>
There was a locking problem where the fip-&gt;lock was held during
the call to update_mac().  The rtnl_lock() must be taken before
the fip-&gt;lock, not the other way around.  This fixes that.

Now that fcoe_ctlr_recv_flog() is called only from the response handler
to a FLOGI request, some checking can be eliminated.  Instead of calling
update_mac(), just fill in the granted_mac address for the passed-in
frame (skb).

Eliminate the passed-in source MAC address since it is also in the skb.

Also, in fcoe, call fcoe_set_src_mac() directly instead of going thru
the fip function pointer.  This will generate less code.
Then, since fip isn't needed for LOGO response, use lport as the arg.

Signed-off-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: don't send ELS in FIP mode if no FCF selected</title>
<updated>2009-12-04T18:01:13Z</updated>
<author>
<name>Joe Eykholt</name>
</author>
<published>2009-11-03T19:48:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f31f2a1c3215e96fbff2152486d0fb590f72634e'/>
<id>urn:sha1:f31f2a1c3215e96fbff2152486d0fb590f72634e</id>
<content type='text'>
If link is up, but no FCF is selected, don't send any ELS frames.

This came up when an fnic received a multicast advertisement but
no solitited advertisments, so no FCF was selected.  It tried
to send FLOGIs anyway.

Signed-off-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: FIP should report link to libfc whether selected or not</title>
<updated>2009-12-04T18:01:13Z</updated>
<author>
<name>Joe Eykholt</name>
</author>
<published>2009-11-03T19:48:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd42dac4ecd1799077c132aab35d3c36b26d4d8c'/>
<id>urn:sha1:dd42dac4ecd1799077c132aab35d3c36b26d4d8c</id>
<content type='text'>
The fnic driver with FIP is reporting link up, even though it's down.

When the interface is shut down by the switch, we receive a clear
virtual link, and set the state reported to libfc as down, although
we still report it up.  Clearly wrong.  That causes the subsequent
link down event not to be reported, and /sys shows the host "Online".

Currently, in FIP mode, if an FCF times out, then link to libfc
is reported as down, to stop FLOGIs.  That interferes with the LLD
link down being reported.

Users really need to know the physical link information, to diagnose
cabling issues, so physical link status should be reported to libfc.

If the selected FCF needs to be reported, that should be done
separately, in a later patch.

Signed-off-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: fip: allow FIP receive to be called from IRQ.</title>
<updated>2009-12-04T18:01:12Z</updated>
<author>
<name>Joe Eykholt</name>
</author>
<published>2009-11-03T19:48:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1f4aed818d26eb9ed54520fbeb85d5ee691baa94'/>
<id>urn:sha1:1f4aed818d26eb9ed54520fbeb85d5ee691baa94</id>
<content type='text'>
FIP's fcoe_ctlr_recv() function was previously only called from
the soft IRQ in FCoE.  It's not performance critical and is more
convenient for some drivers to call it from the IRQ level.  Just
Change to use skb_queue()/dequeue() which uses spinlock_irqsave
instead of separate locking with _bh locks.

Signed-off-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
<entry>
<title>[SCSI] libfcoe: fip: use SCSI host number to identify debug messages.</title>
<updated>2009-12-04T18:01:12Z</updated>
<author>
<name>Joe Eykholt</name>
</author>
<published>2009-11-03T19:48:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0f51c2e54c0bfdb6b02c53f6d7dd9b35f91821b6'/>
<id>urn:sha1:0f51c2e54c0bfdb6b02c53f6d7dd9b35f91821b6</id>
<content type='text'>
Use scsi host number to identify debug messages.
Previously, no instance information was given, so if multiple
ports were active, it became confusing.
Signed-off-by: Joe Eykholt &lt;jeykholt@cisco.com&gt;
Signed-off-by: Robert Love &lt;robert.w.love@intel.com&gt;
Signed-off-by: James Bottomley &lt;James.Bottomley@suse.de&gt;
</content>
</entry>
</feed>
