action (full) in projects: Documentation

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:action (Results 1 – 25 of 256) sorted by relevance

12 3 4 5 6 7 8 9 10 11

/Documentation/networking/devlink/
D	devlink-reload.rst	14 User may select a reload action. 15 By default ``driver_reinit`` action is selected. 38 pending activation. If no limitation specified this action may involve 39 firmware reset. If no new image pending this action will reload current 42 Note that even though user asks for a specific action, the driver 43 implementation might require to perform another action alongside with 54 However, some drivers support action limits, which limit the action 79 …$ devlink dev reload DEV [ netns { PID \| NAME \| ID } ] [ action { driver_reinit \| fw_activate } ] … 82 $ devlink dev reload pci/0000:82:00.0 action driver_reinit 88 $ devlink dev reload pci/0000:82:00.0 action fw_activate
D	devlink-dpipe.rst	`46 modeled as a graph of match/action tables. Each table represents a specific 139 Action section in Model 155 match/action values and specific counter. By dumping the tables content the 188 action: { meta.adj_index: set, 209 action: { ethernet.daddr: set } 229 action: { ethernet.daddr: set, 250 action: { meta.l3_drop: set,`
/Documentation/admin-guide/device-mapper/
D	dm-uevent.rst	`25 :Uevent Action(s): KOBJ_CHANGE 32 :Uevent Action(s): KOBJ_CHANGE 35 :Value: Device-mapper specific action that caused the uevent action. 41 :Uevent Action(s): KOBJ_CHANGE 48 :Uevent Action(s): KOBJ_CHANGE 56 :Uevent Action(s): KOBJ_CHANGE 63 :Uevent Action(s): KOBJ_CHANGE 70 :Uevent Action(s): KOBJ_CHANGE 81 ACTION=change 98 ACTION=change`
/Documentation/networking/
D	tc-queue-filters.rst	`13 using the action skbedit priority for Tx priority selection, 17 2) TC filter directs traffic to a transmit queue with the action 18 skbedit queue_mapping $tx_qid. The action skbedit queue_mapping 30 2) TC filter with action skbedit queue_mapping $rx_qid selects a 31 receive queue. The action skbedit queue_mapping for receive queue`
/Documentation/ABI/testing/
D	sysfs-uevent	11 ACTION [UUID [KEY=VALUE ...] 13 The ACTION is compulsory - it is the name of the uevent 14 action (``add``, ``change``, ``remove``). There is no change 45 ACTION=add
D	usb-uevent	`7 contain ACTION=offline and ERROR=DEAD. 12 ACTION=offline`
D	sysfs-driver-ppi	`49 This attribute shows the platform-specific action that should 51 a requested operation. The format is "<action num>: <action`
D	usb-charger-uevent	`26 ACTION=change 43 ACTION=change`
D	sysfs-kernel-mm-damon	152 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/contexts/<C>/schemes/<S>/action 155 Description: Writing to and reading from this file sets and gets the action 161 Description: Action's target NUMA node id. Supported by only relevant 167 Description: Writing a value to this file sets the action apply interval of 360 respectively. Filter out means the action of the scheme will 366 Description: Reading this file returns the number of regions that the action 373 action of the scheme has tried to be applied in bytes. 378 Description: Reading this file returns the number of regions that the action 385 action of the scheme has successfully applied in bytes. 397 corresponding DAMON-based Operation Scheme's action has tried [all …]
D	ima_policy	`20 rule format: action [condition ...] 22 action: measure \| dont_measure \| appraise \| dont_appraise \| 68 when action is "measure" and func is KEY_CHECK. 70 (eg, ima-ng). Only valid when action is "measure".`
/Documentation/fault-injection/
D	provoke-crashes.rst	15 type of action ("crash point type") either through module arguments when 30 Where in the kernel to trigger the action. It can be 35 Indicates the action to be taken on hitting the crash point. 43 before triggering the action. The default is 10 (except for 52 The special file `DIRECT` will induce the action directly without KPROBE
/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
D	switch-driver.rst	157 $ tc filter add dev eth4 ingress flower src_mac 00:01:02:03:04:05 skip_sw action trap 161 …$ tc filter add dev eth4 ingress protocol 802.1q flower skip_sw vlan_id 100 vlan_prio 3 action drop 165 $ tc filter add dev eth4 ingress matchall action mirred egress redirect dev eth1 172 action trap 174 action mirred egress redirect dev eth3 187 …$ tc filter add block 1 ingress protocol 802.1q flower skip_sw vlan_prio 3 action mirred egress mi… 196 …$ tc filter add block 1 ingress protocol 802.1q flower skip_sw vlan_id 200 action mirred egress mi… 201 …$ tc filter add block 1 ingress protocol 802.1q flower skip_sw vlan_id 200 action mirred egress mi… 204 …$ tc filter add block 1 ingress protocol 802.1q flower skip_sw vlan_id 200 action mirred egress mi… 214 …$ tc filter add block 1 ingress protocol 802.1q flower skip_sw vlan_id 200 action mirred egress mi… [all …]
/Documentation/userspace-api/
D	dcdbas.rst	`51 Host Control Action 61 action after the system has finished shutting down: 68 power off host control action using this driver: 70 1) Write host control action to be performed to host_control_action. 72 3) Write "1" to host_control_on_shutdown to enable host control action. 82 perform a power cycle or power off host control action:`
/Documentation/scsi/
D	scsi_eh.rst	224 highest-severity action means EH failure and results in offlining of 230 eh_work_q. If a recovery action succeeds for a scmd, recovered 233 Note that single recovery action on a scmd can recover multiple 260 :ACTION: scsi_eh_scmd_add() is invoked for scmd 270 :ACTION: move all scmds to EH's local eh_work_q. shost->eh_cmd_q 278 :ACTION: scsi_eh_finish_cmd() is invoked to EH-finish scmd 290 :ACTION: scsi_eh_flush_done_q() retries scmds or notifies upper 313 cleared by this action. 319 This action is taken for each error-completed 324 sync between occurrence of CHECK CONDITION and this action. [all …]
/Documentation/devicetree/bindings/thermal/
D	thermal-zones.yaml	16 take appropriate action to mitigate thermal overloads. 81 critical-action: 84 The action the OS should perform after the critical temperature is reached. 85 By default the system will shutdown as a safe action to prevent damage 87 The shutdown action should be always the default and preferred one. 130 which the thermal framework needs to take action. The actions to 150 millicelsius. Any cooling action initiated by the framework is 154 cooling action is removed. 175 The action to be taken is left to the driver. 195 This node describes the action to be taken when a thermal zone [all …]
/Documentation/security/
D	ipe.rst	136 2. A single, non-customizable action was implicitly taken as a default. 292 in the action being denied. 294 in the action being allowed. 295 3. A policy in which the action taken when no rules are matched is 300 op=EXECUTE integrity_verified=YES action=ALLOW 308 op=EXECUTE integrity_verified=YES action=ALLOW 310 op=READ integrity_verified=NO label=critical_t action=DENY 311 op=READ action=ALLOW 322 op=READ integrity_verified=NO label=critical_t action=DENY 327 op=EXECUTE integrity_verified=YES action=ALLOW [all …]
/Documentation/netlink/specs/
D	ovs_flow.yaml	`257 name: ovs-action-push-vlan 280 name: ovs-action-hash 303 name: ovs-action-push-mpls 321 name: ovs-action-add-mpls 390 nested-attributes: action-attrs 602 name: action-attrs 603 enum-name: ovs-action-attr 604 name-prefix: ovs-action-attr- 622 struct: ovs-action-push-vlan 641 struct: ovs-action-hash [all …]`
D	devlink.yaml	`140 name: dpipe-action-type 160 name: reload-action 187 name: trap-action 338 name: dpipe-entry-action-values 340 nested-attributes: dl-dpipe-entry-action-values 359 name: dpipe-action 362 nested-attributes: dl-dpipe-action 364 name: dpipe-action-value 367 nested-attributes: dl-dpipe-action-value 369 name: dpipe-action-type [all …]`
/Documentation/input/
D	gamepad.rst	`35 D-Pad Left Right Action Pad 43 - Action-Pad 99 - Action-Pad: 101 Every gamepad device has at least 2 action buttons. This means, that every 111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and 117 If only 3 action-buttons are present, they are reported as (from left 124 If all 4 action-buttons are present, they can be aligned in two`
/Documentation/trace/
D	boottime-trace.rst	66 (you can enable it by the "traceon" event trigger action) 111 ftrace.[instance.INSTANCE.]event.GROUP.EVENT.actions = ACTION[, ACTION2[...]] 131 Since it is too long to write a histogram action as a string for per-event 132 action option, there are tree-style options under per-event 'hist' subkey 165 Set histogram 'trace' action for 'onmatch'. 176 Set histogram 'save' action parameters for 'onmax' or 'onchange' handler. 181 Set histogram 'snapshot' action for 'onmax' or 'onchange' handler. 189 option if the 'actions' option has a histogram action. 264 With the trigger action and kprobes, you can trace function-graph while
D	events-power.rst	`78 pm_qos_update_target "action=%s prev_value=%d curr_value=%d" 79 pm_qos_update_flags "action=%s prev_value=0x%x curr_value=0x%x" 81 The first parameter gives the QoS action name (e.g. "ADD_REQ").`
/Documentation/admin-guide/mm/damon/
D	usage.rst	81 │ │ │ │ │ │ :ref:`0 <sysfs_scheme>`/action,target_nid,apply_interval_us 147 action tried regions directory for each DAMON-based operation scheme of the 148 kdamond. For details of the DAMON-based operation scheme action tried 154 action tried regions directory for each DAMON-based operation scheme of the 293 (``action``, ``target_nid`` and ``apply_interval``) exist. 295 The ``action`` file is for setting and getting the scheme's :ref:`action 301 only meaningful when the ``action`` is either ``migrate_hot`` or 337 for applying the ``action`` to memory regions of the ``access_pattern``, and to 338 apply the action to only up to ``bytes`` bytes of memory regions within the 428 or does not match to the type, respectively. Then, the scheme's action will [all …]
/Documentation/translations/zh_CN/core-api/
D	genericirq.rst	`219 handle_irq_event(desc->action); 230 handle_irq_event(desc->action); 252 handle_irq_event(desc->action); 268 handle_irq_event(desc->action); 282 handle_irq_event(desc->action);`
D	memory-hotplug.rst	`56 struct notifier_block self, unsigned long action, void arg); 59 数（action）是上述的事件类型之一。第三个参数（arg）传递一个指向`
/Documentation/mm/damon/
D	design.rst	313 Operation Action 316 The management action that the users desire to apply to the regions of their 322 each action is in the DAMON operations set layer because the implementation 327 specific DAMOS action depends on what operations set is selected to be used 331 that supports each action are as below. 358 To know how user-space can set the action via :ref:`DAMON sysfs interface 359 <sysfs_interface>`, refer to :ref:`action <sysfs_scheme>` part of the 388 action to all pages of the huge region could consume unacceptably large system 395 can use for applying the action, and/or a maximum bytes of memory regions that 396 the action can be applied within a user-specified time duration. [all …]

12 3 4 5 6 7 8 9 10 11

Documentation
LICENSES
arch
block
certs
crypto
drivers
fs
gki
include
init
io_uring
ipc
kernel
lib
mm
net
rust
samples
scripts
security
sound
tools
usr
virt