TASKS;RCU detection of tickless user mode execution as a quiescent state

• US 9,600,349 B2
• Filed: 08/21/2015
• Issued: 03/21/2017
• Est. Priority Date: 05/12/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McKenney, Paul E.
• Primary Examiner(s): Wathen, Brian W
• Application Number:
  US14/832,544
• Publication Number:
  US 20160335133A1
• Time in Patent Office: 578 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms

Abstract

A TASKS_RCU grace period is detected whose quiescent states comprise a task undergoing a voluntary context switch, a task running in user mode, and a task running in idle-mode. A list of all runnable tasks is built. The runnable task list is scanned in one or more scan passes. Each scan pass through the runnable task list searches to identify tasks that have passed through a quiescent state by either performing a voluntary context switch, running in user mode, or running in idle-mode. If found, such quiescent state tasks are removed from the runnable task list. Searching performed during a scan pass includes identifying quiescent state tickless user mode tasks that have been running continuously in user mode on tickless CPUs that have not received a scheduling clock interrupt since commencement of the TASKS_RCU grace period. If the runnable task list is empty, the TASKS_RCU grace period is ended.

Claims

1. In a computer system having a plurality of CPUs operatively coupled to one or more memory devices, a method for detecting a TASKS_RCU grace period whose quiescent states comprise a task undergoing a voluntary context switch, a task running in user mode, and a task running in idle-mode, said method comprising:

building a runnable task list of all runnable tasks in said computer system,

scanning said runnable task list in one or more scan passes;

on each scan pass through said runnable task list, searching to identify quiescent state tasks that have passed through a quiescent state by either performing a voluntary context switch, running in user mode, or running in idle-mode, and if found, removing said quiescent state tasks from said runnable task list;

said searching including identifying quiescent state tickless user mode tasks that have been running continuously in user mode on tickless CPUs that have not received a scheduling clock interrupt since commencement of said TASKS_RCU grace period; and

if said runnable task list is empty, ending said TASKS_RCU grace period.

2. The method of claim 1, wherein said identifying quiescent state tickless user mode tasks includes checking for a tickless task indicator associated with each said quiescent state tickless user mode task.

3. The method of claim 2, wherein said tickless task indicator is set during a CPU'"'"'s entry into tickless mode to indicate that a current task running on said CPU is a tickless user mode task, and reset during a CPU'"'"'s exit from tickless mode to indicate that a current task running on said CPU is not a tickless user mode task.

4. The method of claim 3, wherein said tickless task indicator comprises a task structure variable stored in a task structure for said current task.

5. The method of claim 4, wherein said task structure variable is set by assigning it a CPU number of said CPU on which said current task is running, and wherein said task structure variable is reset by assigning it a predetermined special value.

6. The method of claim 3, wherein said tickless task indicator comprises a per-CPU variable stored in a tickless mode data structure that tracks whether a CPU is in tickless mode.

7. The method of claim 6, wherein said per-CPU variable is set by assigning it a pointer to a task structure of said current task, and wherein said per-CPU variable is reset by assigning it a NULL pointer.