[SCSI] libfc: track FIP exchanges
authorJoe Eykholt <jeykholt@cisco.com>
Tue, 20 Jul 2010 22:20:14 +0000 (15:20 -0700)
committerJames Bottomley <James.Bottomley@suse.de>
Wed, 28 Jul 2010 14:05:54 +0000 (09:05 -0500)
commitf60e12e9c778c8256a646f80603d1b88ba5ce891
tree732e918fc85cc441cd539be5e389e0dfd29a2199
parenta7b12a279faaad26837276065104a1f9cf60e962
[SCSI] libfc: track FIP exchanges

When an exchange is received with a FIP encapsulation, we need
to know that the response must be sent via FIP and what the original
ELS opcode was.  This becomes important for VN2VN mode, where we may
receive FLOGI or LOGO from several peer VN_ports, and the LS_ACC or
LS_RJT must be sent FIP-encapsulated with the correct sub-type.

Add a field to the struct fc_frame, fr_encaps, to indicate the
encapsulation values.  That term is chosen to be neutral and
LLD-agnostic in case non-FCoE/FIP LLDs might find it useful.

The frame fr_encaps is transferred from the ingress frame to the
exchange by fc_exch_recv_req(), and back to the outgoing frame
by fc_seq_send().

This is taking the last byte in the skb->cb array.  If needed,
we could combine the info in sof, eof, flags, and encaps
together into one field, but it'd be better to do that if
and when its needed.

Signed-off-by: Joe Eykholt <jeykholt@cisco.com>
Signed-off-by: Robert Love <robert.w.love@intel.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
drivers/scsi/libfc/fc_exch.c
include/scsi/fc_frame.h
include/scsi/libfc.h
This page took 0.025978 seconds and 5 git commands to generate.