Searched full:target (Results 1 – 25 of 340) sorted by relevance
12345678910>>...14
| /Documentation/target/ |
| D | tcm_mod_builder.rst | 13 mkdir -p /sys/kernel/config/target/$TCM_NEW_MOD
15 This script will create a new drivers/target/$TCM_NEW_MOD/, and will do the following
17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
23 the TransportID / Initiator and Target WWPN related handlers for
25 using drivers/target/target_core_fabric_lib.c logic.
32 …target:/mnt/sdb/lio-core-2.6.git/Documentation/target# python tcm_mod_builder.py -p iSCSI -m tcm_n…
33 tcm_dir: /mnt/sdb/lio-core-2.6.git/Documentation/target/../../
36 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
39 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000
41 /mnt/sdb/lio-core-2.6.git/Documentation/target/../../drivers/target/tcm_nab5000/tcm_nab5000_base.h
[all …]
|
| D | target-export-device | 4 # create a very simple LIO iSCSI target with a file or block device
13 Export a block device or a file as an iSCSI target with a single LUN
37 CORE_DIR=$CONFIGFS/target/core
38 ISCSI_DIR=$CONFIGFS/target/iscsi
40 # Load the target modules and mount the config file system
61 # Create an iSCSI target and a target portal group (TPG)
80 echo "Target ${IQN}, portal ${PORTAL} has been created"
|
| D | scripts.rst | 7 Target export device script
10 .. literalinclude:: target-export-device
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 1 Texas Instruments sysc interconnect target module wrapper binding
3 Texas Instruments SoCs can have a generic interconnect target module
10 Each interconnect target module can have one or more devices connected to
11 it. There is a set of control registers for managing interconnect target
16 target module and typically are named REVISION, SYSCONFIG and SYSSTATUS.
44 target module in question such as revision, sysc and syss
47 interconnect target module in question such as
50 - ranges shall contain the interconnect target module IO range
52 by the interconnect target module, the ranges may include
60 Manual (TRM) for the interconnect target module
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-ib_srp | 5 Description: Interface for making ib_srp connect to a new target.
6 One can request ib_srp to connect to a new target by writing
11 byte identifier extension in the 16-byte SRP target port
12 identifier. The target port identifier is sent by ib_srp
13 to the target in the SRP_LOGIN_REQ request.
15 byte I/O controller GUID portion of the 16-byte target port
23 the SRP target. How to find out the value of the service ID
24 is specified in the documentation of the SRP target.
31 class defines the format of the SRP initiator and target
35 identifier. This data is sent by the initiator to the target
[all …]
|
| D | sysfs-bus-firewire | 114 What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
116 /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
121 SCSI target port identifier and logical unit identifier of a
122 logical unit of an SBP-2 target. The identifiers are specified
124 unique properties the SBP-2 attached target.
126 Read-only attribute, immutable during the target's lifetime.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 5 The dm-integrity target emulates a block device that has additional
12 To guarantee write atomicity, the dm-integrity target uses journal, it
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
23 The dm-integrity target can also be used as a standalone target, in this
25 mode, the dm-integrity target can be used to detect silent data
36 When loading the target for the first time, the kernel driver will format
39 target can't be loaded.
41 To use the target for the first time:
[all …]
|
| D | persistent-data.rst | 13 - Heinz Mauelshagen's thin provisioning target
14 - Another btree-based caching target posted to dm-devel
15 - Another multi-snapshot target based on a design of Daniel Phillips
22 targets. It's currently used by the thin-provisioning target and an
23 upcoming hierarchical storage target.
83 thin-provisioning target uses a btree with two levels of nesting.
|
| D | dm-init.rst | 37 Target types
40 Not all target types are available as there are serious risks in allowing
59 `thin` constrained, requires dm target message from userspace
60 `thin-pool` constrained, requires dm target message from userspace
66 If the target is not listed above, it is constrained by default (not tested).
75 This will boot to a rw dm-linear target of 8192 sectors split across two block
77 this target to /dev/mapper/lroot (depending on the rules). No uuid was assigned.
90 Other examples (per target):
|
| D | era.rst | 8 dm-era is a target that behaves similar to the linear target. In
10 defined period of time called an 'era'. Each era target instance
27 tracked by the target
73 snapshot was the primary use case when developing this target:
78 - Send a checkpoint message to the era target
97 The target uses a bitset to record writes in the current era. It also
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 21 (effective) target value. The aggregated target value is updated with changes
23 aggregated target value is simply the min of the request values held in the list
26 Note: the aggregated target value is implemented as an atomic variable so that
32 Will insert an element into the CPU latency QoS list with the target value.
33 Upon change to this list the new target is recomputed and any registered
34 notifiers are called only if the target value is now different.
39 Will update the list element pointed to by the handle with the new target
40 value and recompute the new aggregated target, calling the notification tree
41 if the target is changed.
44 Will remove the element. After removal it will update the aggregate target
[all …]
|
| /Documentation/driver-api/ |
| D | target.rst | 2 target and iSCSI Interfaces Guide
10 Target core device interfaces
14 drivers/target/target_core_device.c.
16 Target core transport interfaces
19 .. kernel-doc:: drivers/target/target_core_transport.c
22 Target-supported userspace I/O
25 .. kernel-doc:: drivers/target/target_core_user.c
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 32 performance full-duplex serial link between the debug target
44 On the debug target system, you need to customize a debugging
60 Before starting the debug target, you should connect the debug
65 During early boot of the debug target, DbC will be detected and
67 to enumerate the debug device in debug target. The debug host
113 root@target:/sys/bus/pci/devices/0000:00:14.0# cat dbc
118 root@target:/sys/bus/pci/devices/0000:00:14.0# echo enable > dbc
122 root@target:/sys/bus/pci/devices/0000:00:14.0# cat dbc
125 Connect the debug target to the debug host with a USB 3.0 super-
127 on the debug target. You will see below kernel message lines::
[all …]
|
| /Documentation/block/ |
| D | kyber-iosched.rst | 5 The only two tunables for the Kyber scheduler are the target latencies for
7 these target latencies.
11 Target latency for reads (in nanoseconds).
15 Target latency for synchronous writes (in nanoseconds).
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-examples.rst | 8 ``V4L2_BUF_TYPE_VIDEO_CAPTURE`` for other devices; change target to
18 .target = V4L2_SEL_TGT_CROP_DEFAULT,
23 sel.target = V4L2_SEL_TGT_CROP;
38 .target = V4L2_SEL_TGT_COMPOSE_BOUNDS,
51 sel.target = V4L2_SEL_TGT_COMPOSE;
67 .target = V4L2_SEL_TGT_COMPOSE,
71 .target = V4L2_SEL_TGT_CROP,
|
| D | selection-api-configuration.rst | 32 target. It is recommended for the driver developers to put the top/left
37 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
44 ``V4L2_SEL_TGT_CROP_DEFAULT`` target. This rectangle shall cover what the
56 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
109 target. The rectangle's coordinates are expressed in pixels. The
115 ``V4L2_SEL_TGT_COMPOSE_DEFAULT`` target. This rectangle shall cover what
125 equal to active one. The padded target is accessed by the
127 from the ``V4L2_SEL_TGT_COMPOSE`` target.
|
| D | vidioc-subdev-g-selection.rst | 46 See :ref:`subdev` for more information on how each selection target
58 targets are the targets which configure the hardware. The BOUNDS target
65 ``VIDIOC_SUBDEV_G_SELECTION`` on them. Any unsupported target will
88 - ``target``
89 - Target selection rectangle. See :ref:`v4l2-selections-common`.
118 references a non-existing format, or the selection target is not
|
| D | selection-api-intro.rst | 15 cropping target determine the area actually sampled. The sink is an
20 and the cropping target is a part of an image to be shown on a display.
23 and position of such a window is controlled by the compose target.
|
| /Documentation/scsi/ |
| D | BusLogic.rst | 105 requested and negotiated with each target device. AutoSCSI settings for
107 reported for each target device, as well as the status of Tagged Queuing.
108 If the same setting is in effect for all target devices, then a single word
109 or phrase is used; otherwise, a letter is provided for each target device to
115 Synchronous negotiation is enabled for all target devices and the host
120 Synchronous negotiation is enabled for all target devices and the host
125 Synchronous negotiation is enabled for all target devices and the host
130 Synchronous negotiation is disabled and all target devices are limited to
135 Synchronous negotiation to Ultra speed is enabled for target devices 0
136 and 4 through 15, to Fast speed for target device 1, to Slow speed for
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-platform.txt | 32 - target-supply : regulator for SATA target power
50 - target-supply : regulator for SATA target power
71 target-supply = <®_sata0>;
77 target-supply = <®_sata1>;;
|
| D | allwinner,sun4i-a10-ahci.yaml | 28 target-supply:
29 description: Regulator for SATA target power
46 target-supply = <®_ahci_5v>;
|
| /Documentation/sphinx/ |
| D | automarkup.py | 131 target = match.group(2)
134 if not (target in Skipfuncs or target in Skipnames):
140 reftarget = target, modname = None,
148 reftype_s, target, pxref,
182 target = match.group(2)
185 if not ((match.re == RE_function and target in Skipfuncs)
186 or (target in Skipnames)):
191 reftarget = target, modname = None,
199 reftype_str[match.re], target, pxref,
220 target = match.group(1)
[all …]
|
| /Documentation/ia64/ |
| D | irq-redir.rst | 13 IRQ target is one particular CPU and cannot be a mask of several
20 The target CPU has to be specified as a hexadecimal CPU mask. The
38 gives the target CPU mask for the specified interrupt vector. If the CPU
49 IO-SAPIC interrupts are initialized with CPU#0 as their default target
64 routing is used. The target CPUs are distributed in a round robin
65 manner. IRQs will be routed only to the selected target CPUs. Check
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 26 the parent and finds source and target. Then we decide which of the
27 source and target need to be locked. Source needs to be locked if it's a
28 non-directory; target - if it's a non-directory or about to be removed.
30 to take both (that can happen only when both source and target are
32 and the target because mixing directory and non-directory is allowed
33 only with RENAME_EXCHANGE, and that won't be removing the target).
51 * find source and target.
52 * if old parent is equal to or is a descendent of target
56 * Lock subdirectories involved (source before target).
91 target in inode pointer order in the case they are not directories.)
|
| /Documentation/ABI/testing/ |
| D | sysfs-ibft | 12 files that expose the iSCSI Boot Firmware Table target data.
13 Usually this contains the target's IP address, boot LUN,
14 target name, and what NIC it is associated with. It can also
|
12345678910>>...14