Searched full:target (Results 1 – 25 of 311) sorted by relevance
12345678910>>...13
| /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.
43 target module in question such as revision, sysc and syss
46 interconnect target module in question such as
49 - ranges shall contain the interconnect target module IO range
51 by the interconnect target module, the ranges may include
59 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
10 byte identifier extension in the 16-byte SRP target port
11 identifier. The target port identifier is sent by ib_srp
12 to the target in the SRP_LOGIN_REQ request.
14 byte I/O controller GUID portion of the 16-byte target port
22 the SRP target. How to find out the value of the service ID
23 is specified in the documentation of the SRP target.
30 class defines the format of the SRP initiator and target
34 identifier. This data is sent by the initiator to the target
[all …]
|
| D | sysfs-bus-firewire | 113 What: /sys/bus/firewire/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
115 /sys/bus/ieee1394/drivers/sbp2/fw*/host*/target*/*:*:*:*/ieee1394_id
120 SCSI target port identifier and logical unit identifier of a
121 logical unit of an SBP-2 target. The identifiers are specified
123 unique properties the SBP-2 attached target.
125 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 | 32 an aggregated target value. The aggregated target value is updated with
34 aggregated target value is simply the max or min of the request values held
36 Note: the aggregated target value is implemented as an atomic variable so that
44 target value. Upon change to this list the new target is recomputed and any
45 registered notifiers are called only if the target value is now different.
50 Will update the list element pointed to by the handle with the new target value
51 and recompute the new aggregated target, calling the notification tree if the
52 target is changed.
55 Will remove the element. After removal it will update the aggregate target and
56 call the notification tree if the target was changed as a result of removing
[all …]
|
| /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/scsi/ |
| D | BusLogic.txt | 95 requested and negotiated with each target device. AutoSCSI settings for
97 reported for each target device, as well as the status of Tagged Queuing.
98 If the same setting is in effect for all target devices, then a single word
99 or phrase is used; otherwise, a letter is provided for each target device to
105 Synchronous negotiation is enabled for all target devices and the host
110 Synchronous negotiation is enabled for all target devices and the host
115 Synchronous negotiation is enabled for all target devices and the host
120 Synchronous negotiation is disabled and all target devices are limited to
125 Synchronous negotiation to Ultra speed is enabled for target devices 0
126 and 4 through 15, to Fast speed for target device 1, to Slow speed for
[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/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/media/uapi/v4l/ |
| D | selection-api-examples.rst | 15 ``V4L2_BUF_TYPE_VIDEO_CAPTURE`` for other devices; change target to
25 .target = V4L2_SEL_TGT_CROP_DEFAULT,
30 sel.target = V4L2_SEL_TGT_CROP;
45 .target = V4L2_SEL_TGT_COMPOSE_BOUNDS,
58 sel.target = V4L2_SEL_TGT_COMPOSE;
74 .target = V4L2_SEL_TGT_COMPOSE,
78 .target = V4L2_SEL_TGT_CROP,
|
| D | vidioc-subdev-g-selection.rst | 53 See :ref:`subdev` for more information on how each selection target
61 targets are the targets which configure the hardware. The BOUNDS target
69 ``VIDIOC_SUBDEV_G_SELECTION`` on them. Any unsupported target will
93 - ``target``
94 - Target selection rectangle. See :ref:`v4l2-selections-common`.
124 references a non-existing format, or the selection target is not
|
| D | selection-api-configuration.rst | 39 target. It is recommended for the driver developers to put the top/left
44 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
51 ``V4L2_SEL_TGT_CROP_DEFAULT`` target. This rectangle shall cover what the
63 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
116 target. The rectangle's coordinates are expressed in pixels. The
122 ``V4L2_SEL_TGT_COMPOSE_DEFAULT`` target. This rectangle shall cover what
132 equal to active one. The padded target is accessed by the
134 from the ``V4L2_SEL_TGT_COMPOSE`` target.
|
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-platform.txt | 34 - target-supply : regulator for SATA target power
54 - target-supply : regulator for SATA target power
68 target-supply = <®_ahci_5v>;
83 target-supply = <®_sata0>;
89 target-supply = <®_sata1>;;
|
| /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. In case of exchange (with
28 if the target already exists, lock it. If the source is a non-directory,
31 NB: we might get away with locking the the source (and target in exchange
48 * find source and target.
49 * if old parent is equal to or is a descendent of target
53 * If it's an exchange, lock both the source and the target.
54 * If the target exists, lock it. If the source is a non-directory,
59 the the source (and target in exchange case) shared.
88 target in inode pointer order in the case they are not directories.)
|
| /Documentation/networking/ |
| D | netconsole.txt | 95 To add a remote logging target (target names can be arbitrary):
105 To remove a target:
109 The interface exposes these parameters of a netconsole target to userspace:
111 enabled Is this target currently enabled? (read-write)
122 a target can be updated or not -- you can modify the parameters of only
125 To update a target's parameters:
128 echo 0 > enabled # disable the target (if required)
132 echo 1 > enabled # enable target again
171 WARNING: the default target ethernet setting uses the broadcast
|
| D | netfilter-sysctl.txt | 8 with LOG target; this aims to prevent containers from flooding host
9 kernel log. If enabled, this target also works in other network
|
| /Documentation/devicetree/ |
| D | overlay-notes.txt | 44 target = <&ocp>;
119 target=<phandle>; /* phandle target of the overlay */
121 target-path="/path"; /* target path of the overlay */
124 property-a; /* add property-a to the target */
136 Using the non-phandle based target method allows one to use a base DT which does
138 The __symbols__ node is only required for the target=<phandle> method, since it
|
| /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>>...13