1FC_REMOTE_PORT_ADD(9)           SCSI mid layer           FC_REMOTE_PORT_ADD(9)
2
3
4

NAME

6       fc_remote_port_add - notify fc transport of the existence of a remote
7       FC port.
8

SYNOPSIS

10       struct fc_rport * fc_remote_port_add(struct Scsi_Host * shost,
11                                            int channel,
12                                            struct fc_rport_identifiers * ids);
13

ARGUMENTS

15       shost
16           scsi host the remote port is connected to.
17
18       channel
19           Channel on shost port connected to.
20
21       ids
22           The world wide names, fc address, and FC4 port roles for the remote
23           port.
24

DESCRIPTION

26       The LLDD calls this routine to notify the transport of the existence of
27       a remote port. The LLDD provides the unique identifiers (wwpn,wwn) of
28       the port, it's FC address (port_id), and the FC4 roles that are active
29       for the port.
30
31       For ports that are FCP targets (aka scsi targets), the FC transport
32       maintains consistent target id bindings on behalf of the LLDD. A
33       consistent target id binding is an assignment of a target id to a
34       remote port identifier, which persists while the scsi host is attached.
35       The remote port can disappear, then later reappear, and it's target id
36       assignment remains the same. This allows for shifts in FC addressing
37       (if binding by wwpn or wwnn) with no apparent changes to the scsi
38       subsystem which is based on scsi host number and target id values.
39       Bindings are only valid during the attachment of the scsi host. If the
40       host detaches, then later re-attaches, target id bindings may change.
41
42       This routine is responsible for returning a remote port structure. The
43       routine will search the list of remote ports it maintains internally on
44       behalf of consistent target id mappings. If found, the remote port
45       structure will be reused. Otherwise, a new remote port structure will
46       be allocated.
47
48       Whenever a remote port is allocated, a new fc_remote_port class device
49       is created.
50
51       Should not be called from interrupt context.
52

NOTES

54       This routine assumes no locks are held on entry.
55

AUTHORS

57       James Bottomley <James.Bottomley@hansenpartnership.com>
58           Author.
59
60       Rob Landley <rob@landley.net>
61           Author.
62

64Kernel Hackers Manual 2.6.       November 2011           FC_REMOTE_PORT_ADD(9)
Impressum