Home
last modified time | relevance | path

Searched full:target (Results 1 – 25 of 480) sorted by relevance

12345678910>>...20

/Documentation/target/
Dtcm_mod_builder.rst13 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 …]
Dtarget-export-device4 # 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"
/Documentation/devicetree/bindings/net/
Dmscc,vsc7514-switch.yaml58 - description: system target
59 - description: rewriter target
60 - description: qs target
61 - description: PTP target
62 - description: Port0 target
63 - description: Port1 target
64 - description: Port2 target
65 - description: Port3 target
66 - description: Port4 target
67 - description: Port5 target
[all …]
/Documentation/ABI/stable/
Dsysfs-driver-ib_srp5 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 …]
/Documentation/power/
Dpm_qos_interface.rst21 (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/devicetree/bindings/bus/
Dti-sysc.yaml7 title: Texas Instruments interconnect target module
13 Texas Instruments SoCs can have a generic interconnect target module
20 Each interconnect target module can have one or more devices connected to
21 it. There is a set of control registers for managing the interconnect target
24 The interconnect target module control registers are sprinkled into the
26 the interconnect target module. Typically the register names are REVISION,
31 pattern: "^target-module(@[0-9a-f]+)?$"
58 Interconnect target module control registers consisting of
66 Interconnect target module control register names consisting
80 description: Target module power domain if available.
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-integrity.rst5 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.
50 To use the target for the first time:
[all …]
Dpersistent-data.rst13 - 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.
Dvdo.rst6 The dm-vdo (virtual data optimizer) device mapper target provides
8 mapper target, it can add these features to the storage stack, compatible
9 with any file system. The vdo target does not protect against data
22 In most cases, a vdo target will recover from a crash automatically the
24 error (either during normal operation or crash recovery) the target will
29 the vdo target will rebuild its metadata the next time it is
31 internally consistent and the target will be writable again.
34 inspect a vdo target's on-disk metadata. Fortunately, these tools are
48 Target interface
245 dmsetup message <target-name> 0 <message-name> <message-parameters>
[all …]
Dera.rst8 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
Ddm-init.rst37 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):
/Documentation/driver-api/
Dtarget.rst2 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/
Dusb3-debug-port.rst32 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/i2c/
Dsummary.rst34 The I2C bus connects one or more controller chips and one or more target chips.
50 A **target** chip is a node that responds to communications when addressed by a
53 target (needs hardware support) and respond to another controller on the bus.
54 This is then called a **local target**. In contrast, an external chip is called
55 a **remote target**.
57 Target drivers are kept in a directory specific to the feature they provide,
63 each target.
69 "adapter" for controller and "client" for target. A number of data structures
77 In earlier I2C specifications, controller was named "master" and target was
82 target. Work to replace the old terminology in the Linux Kernel is on-going.
/Documentation/scsi/
DBusLogic.rst105 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/block/
Dkyber-iosched.rst5 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/
Dselection-api-examples.rst8 ``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,
Dselection-api-configuration.rst32 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.
/Documentation/devicetree/bindings/phy/
Dphy-stm32-usbphyc.yaml129 - <0> = 18.87 mA target current / nominal + 0%
130 - <1> = 19.165 mA target current / nominal + 1.56%
131 - <2> = 19.46 mA target current / nominal + 3.12%
132 - <3> = 19.755 mA target current / nominal + 4.68%
133 - <4> = 20.05 mA target current / nominal + 6.24%
134 - <5> = 20.345 mA target current / nominal + 7.8%
135 - <6> = 20.64 mA target current / nominal + 9.36%
136 - <7> = 20.935 mA target current / nominal + 10.92%
137 - <8> = 21.23 mA target current / nominal + 12.48%
138 - <9> = 21.525 mA target current / nominal + 14.04%
[all …]
/Documentation/sphinx/
Dautomarkup.py131 def failure_seen(target): argument
132 return (target) in failed_lookups
133 def note_failure(target): argument
134 failed_lookups[target] = True
155 for target in possible_targets:
156 if (target not in Skipfuncs) and not failure_seen(target):
161 reftarget = target,
170 'function', target, pxref,
177 note_failure(target)
215 for target in possible_targets:
[all …]
/Documentation/filesystems/
Ddirectory-locking.rst43 * find the source and target
44 * decide which of the source and target need to be locked.
45 The source needs to be locked if it's a non-directory, target - if it's
48 if need to take both (that can happen only when both source and target
50 otherwise and the target because mixing directory and non-directory is
51 allowed only with RENAME_EXCHANGE, and that won't be removing the target).
59 * find the source and target.
60 * verify that the source is not a descendent of the target and
61 target is not a descendent of source; fail the operation otherwise.
62 * lock the subdirectories involved (exclusive), source before target.
[all …]
/Documentation/admin-guide/perf/
Dhisi-pcie-pmu.rst64 1. Target filter
66 PMU could only monitor the performance of traffic downstream target Root
67 Ports or downstream target Endpoint. PCIe PMU driver support "port" and
77 "port" filter can be used in all PCIe PMU events, target Root Port can be
82 For example, if target Root Port is 0000:00:00.0 (x8 lanes), bit0 of
83 bitmap should be set, port=0x1; if target Root Port is 0000:00:04.0 (x4
93 "bdf" filter can only be used in bandwidth events, target Endpoint is
95 message requested by target Endpoint.
97 For example, "bdf=0x3900" means BDF of target Endpoint is 0000:39:00.0.
/Documentation/devicetree/bindings/ata/
Dallwinner,sun4i-a10-ahci.yaml28 target-supply:
29 description: Regulator for SATA target power
46 target-supply = <&reg_ahci_5v>;
/Documentation/kbuild/
Dgendwarfksyms.rst116 version\0type\0target\0value\0
124 - `target`: Specifies the target of the rule, typically the fully
131 #define ___KABI_RULE(hint, target, value) \
135 "1\0" #hint "\0" target "\0" value
137 #define __KABI_RULE(hint, target, value) \
138 ___KABI_RULE(hint, #target, #value)
158 - `target`: The fully qualified name of the target data structure
185 - `target`: The fully qualified name of the target enum
210 - `target`: The fully qualified name of the target enum
246 - `target`: The fully qualified name of the target data structure
[all …]
/Documentation/admin-guide/mm/damon/
Dusage.rst229 to ``N-1``. Each directory represents each monitoring target.
236 In each target directory, one file (``pid_target``) and one directory
239 If you wrote ``vaddr`` to the ``contexts/<N>/operations``, each target should
249 required to set the monitoring target address ranges. In case of ``vaddr``
254 For such cases, users can explicitly set the initial monitoring target regions
259 to ``N-1``. Each directory represents each initial monitoring target region.
267 can set and get the start and end addresses of the initial monitoring target
300 The ``target_nid`` file is for setting the migration target node, which is
312 The directory for the target access :ref:`pattern
419 specific address range (an open-ended interval), or ``target`` for specific
[all …]

12345678910>>...20