| /kernel/linux/linux-6.6/rust/kernel/ |
| D | task.rs | 16 unsafe { &*$crate::task::Task::current() }
65 pub struct Task(pub(crate) Opaque<bindings::task_struct>); struct
71 unsafe impl Send for Task {} implementation
76 unsafe impl Sync for Task {} implementation
81 impl Task { impl
90 pub unsafe fn current() -> impl Deref<Target = Task> { in current()
92 task: &'a Task, in current()
97 type Target = Task; in current()
117 pub fn group_leader(&self) -> &Task { in group_leader() argument
151 unsafe impl crate::types::AlwaysRefCounted for Task { implementation
|
| /kernel/liteos_m/components/shell/ |
| D | Kconfig | 17 int "Shell Task Priority"
23 int "Shell Task Stack Size"
|
| /kernel/linux/linux-6.6/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 307 The next diagram shows the situation after the arrival of Task A and
308 Task B at the leftmost and rightmost leaf ``rcu_node`` structures,
317 Suppose that Task A wins, recording its desired grace-period sequence
322 Task A now advances to initiate a new grace period, while Task B moves
351 Task A now acquires the ``rcu_state`` structure's ``->exp_mutex`` and
359 Task F blocking on the root ``rcu_node`` structure and Task E wait for
360 Task A to finish so that it can start the next grace period. The
365 Once the grace period completes, Task A starts waking up the tasks
372 Task E can then acquire ``->exp_mutex`` and increment
380 occupied. However, at some point, Task A will wake up the tasks blocked
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 307 The next diagram shows the situation after the arrival of Task A and
308 Task B at the leftmost and rightmost leaf ``rcu_node`` structures,
317 Suppose that Task A wins, recording its desired grace-period sequence
322 Task A now advances to initiate a new grace period, while Task B moves
351 Task A now acquires the ``rcu_state`` structure's ``->exp_mutex`` and
359 Task F blocking on the root ``rcu_node`` structure and Task E wait for
360 Task A to finish so that it can start the next grace period. The
365 Once the grace period completes, Task A starts waking up the tasks
372 Task E can then acquire ``->exp_mutex`` and increment
380 occupied. However, at some point, Task A will wake up the tasks blocked
[all …]
|
| /kernel/uniproton/build/uniproton_config/config_m4/ |
| D | defconfig | 65 # Task module Configuration
|
| /kernel/uniproton/src/core/kernel/task/ |
| D | Kconfig | 1 menu "Task module Configuration"
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-deadline.rst | 2 Deadline Task Scheduling
19 4.2 Task interface
230 A Task T1
240 A Task T2
263 Suppose Task T1 is the first task to start execution.
269 Task T1 therefore enters the ActiveNonContending state. Since its remaining
271 Task T2 start execution, with runtime still decreased as dq = -1 dt since
276 This is the 0-lag time for Task T1. Since it didn't woken up in the
279 Task T2 continues its execution. However, its runtime is now decreased as
281 Task T2 therefore reclaims the bandwidth unused by Task T1.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-deadline.rst | 2 Deadline Task Scheduling
19 4.2 Task interface
227 A Task T1
237 A Task T2
260 Suppose Task T1 is the first task to start execution.
266 Task T1 therefore enters the ActiveNonContending state. Since its remaining
268 Task T2 start execution, with runtime still decreased as dq = -1 dt since
273 This is the 0-lag time for Task T1. Since it didn't woken up in the
276 Task T2 continues its execution. However, its runtime is now decreased as
278 Task T2 therefore reclaims the bandwidth unused by Task T1.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ufs.rst | 62 Task Manager and Device manager. The UFS interface is designed to be
70 * Task manager:
93 * UTP_TM_SAP: Task management service access point is exposed to task
|
| D | cxgb3i.rst | 27 on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | cxgb3i.rst | 27 on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
|
| D | ufs.rst | 64 Task Manager and Device manager. The UFS interface is designed to be
72 * Task manager:
95 * UTP_TM_SAP: Task management service access point is exposed to task
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | omap-smc.S | 68 mov r6, #0xff @ Indicate new Task call
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| D | omap-smc.S | 68 mov r6, #0xff @ Indicate new Task call
|
| /kernel/liteos_m/components/trace/ |
| D | Kconfig | 73 bool "Via Trace Agent Task"
|
| /kernel/liteos_m/arch/arm/cortex-m33/iar/NTZ/ |
| D | los_exc.S | 231 ; exc occurred in Task or Init or exc
243 ; exc occurred in Task
|
| /kernel/liteos_m/arch/arm/cortex-m55/iar/TZ/non_secure/ |
| D | los_exc.S | 220 ; exc occurred in Task or Init or exc
232 ; exc occurred in Task
|
| /kernel/liteos_m/arch/arm/cortex-m55/iar/NTZ/ |
| D | los_exc.S | 231 ; exc occurred in Task or Init or exc
243 ; exc occurred in Task
|
| /kernel/liteos_m/arch/arm/cortex-m33/iar/TZ/non_secure/ |
| D | los_exc.S | 220 ; exc occurred in Task or Init or exc
232 ; exc occurred in Task
|
| /kernel/liteos_m/arch/arm/cortex-m7/iar/ |
| D | los_exc.S | 231 ; exc occurred in Task or Init or exc
243 ; exc occurred in Task
|
| /kernel/liteos_a/kernel/extended/trace/ |
| D | Kconfig | 73 bool "Via Trace Agent Task"
|
| /kernel/linux/linux-6.6/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 554 * Added a TaskType of Clear Task Set to SCSI
555 * Task Management request.
556 * 12-07-04 01.05.02 Added support for Task Management Query Task.
568 * 03-27-06 01.05.07 Added Task Management type of Clear ACA.
569 * 10-11-06 01.05.08 Shortened define for Task Management type of Clear ACA.
570 * 02-28-07 01.05.09 Defined two new MsgFlags bits for SCSI Task Management
571 * Request: Do Not Send Task IU and Soft Reset Option.
611 * Task buffer, and SSP Status IU.
|
| /kernel/linux/linux-5.10/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 554 * Added a TaskType of Clear Task Set to SCSI
555 * Task Management request.
556 * 12-07-04 01.05.02 Added support for Task Management Query Task.
568 * 03-27-06 01.05.07 Added Task Management type of Clear ACA.
569 * 10-11-06 01.05.08 Shortened define for Task Management type of Clear ACA.
570 * 02-28-07 01.05.09 Defined two new MsgFlags bits for SCSI Task Management
571 * Request: Do Not Send Task IU and Soft Reset Option.
611 * Task buffer, and SSP Status IU.
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/scheduler/ |
| D | schedutil.rst | 89 …- Documentation/translations/zh_CN/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utiliza…
|
| /kernel/liteos_a/kernel/ |
| D | Kconfig | 23 bool "Enable Synchronized Task Operations"
|