diff options
author | Boaz Harrosh <bharrosh@panasas.com> | 2009-11-29 16:26:45 +0200 |
---|---|---|
committer | James Bottomley <James.Bottomley@suse.de> | 2009-12-04 12:01:46 -0600 |
commit | 2cdd6410e5a1665823f2a048fc7f8f6a8384be1d (patch) | |
tree | 327ae154abd84aea9c18eb24eb87c9d6f8029d26 /net/ipv4/tcp_diag.c | |
parent | d6ae4333e648492721a098bdc329bbd82d25eb67 (diff) | |
download | talos-op-linux-2cdd6410e5a1665823f2a048fc7f8f6a8384be1d.tar.gz talos-op-linux-2cdd6410e5a1665823f2a048fc7f8f6a8384be1d.zip |
[SCSI] libosd: osd_dev_info: Unique Identification of an OSD device
Define an osd_dev_info structure that Uniquely identifies an OSD
device lun on the network. The identification is built from unique
target attributes and is the same for all network/SAN machines.
osduld_info_lookup() - NEW
New API that will lookup an osd_dev by its osd_dev_info.
This is used by pNFS-objects for cross network global device
identification. And by exofs multy-device support, the device
info is specified in the on-disk exofs device table.
osduld_device_info() - NEW
Given an osd_dev handle returns its associated osd_dev_info.
The ULD fetches this information at startup and hangs it on
each OSD device. (This is a fast operation that can be called
at any condition)
osduld_device_same() - NEW
With a given osd_dev at one hand and an osd_dev_info
at another, we would like to know if they are the same
device.
Two osd_dev handles can be checked by:
osduld_device_same(od1, osduld_device_info(od2));
osd_auto_detect_ver() - REVISED
Now returns an osd_dev_info structure. Is only called once
by ULD as before. See added comments for how to use.
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'net/ipv4/tcp_diag.c')
0 files changed, 0 insertions, 0 deletions