From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753521AbaHLPua (ORCPT ); Tue, 12 Aug 2014 11:50:30 -0400 Received: from service87.mimecast.com ([91.220.42.44]:53031 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753300AbaHLPts (ORCPT ); Tue, 12 Aug 2014 11:49:48 -0400 From: Juri Lelli To: peterz@infradead.org Cc: luca.abeni@unitn.it, rdunlap@infradead.org, mingo@redhat.com, henrik@austad.us, raistlin@linux.it, juri.lelli@gmail.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Juri Lelli Subject: [PATCH 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Date: Tue, 12 Aug 2014 16:49:15 +0100 Message-Id: <1407858555-14371-5-git-send-email-juri.lelli@arm.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1407858555-14371-1-git-send-email-juri.lelli@arm.com> References: <1407858555-14371-1-git-send-email-juri.lelli@arm.com> X-OriginalArrivalTime: 12 Aug 2014 15:49:44.0095 (UTC) FILETIME=[093BDAF0:01CFB645] X-MC-Unique: 114081216494702001 Content-Type: text/plain; charset=WINDOWS-1252 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id s7CFp3gc014553 Add an appendix briefly describing tools that can be used to test SCHED_DEADLINE (and the scheduler in general). Links to where source code of the tools is hosted are also provided. Signed-off-by: Juri Lelli Cc: Randy Dunlap Cc: Peter Zijlstra Cc: Ingo Molnar Cc: Henrik Austad Cc: Dario Faggioli Cc: Juri Lelli Cc: linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org --- Documentation/scheduler/sched-deadline.txt | 52 ++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/Documentation/scheduler/sched-deadline.txt b/Documentation/scheduler/sched-deadline.txt index d056034..52eb25f 100644 --- a/Documentation/scheduler/sched-deadline.txt +++ b/Documentation/scheduler/sched-deadline.txt @@ -15,6 +15,7 @@ CONTENTS 5. Tasks CPU affinity 5.1 SCHED_DEADLINE and cpusets HOWTO 6. Future plans + A. Test suite 0. WARNING @@ -339,3 +340,54 @@ CONTENTS throttling patches [https://lkml.org/lkml/2010/2/23/239] but we still are in the preliminary phases of the merge and we really seek feedback that would help us decide on the direction it should take. + +Appendix A. Test suite +====================== + + The SCHED_DEADLINE policy can be easily tested using two applications that + are part of a wider Linux Scheduler validation suite. The suite is + available as a GitHub repository: https://github.com/scheduler-tools. + + The first testing application is called rt-app and can be used to + start multiple threads with specific parameters. rt-app supports + SCHED_{OTHER,FIFO,RR,DEADLINE} scheduling policies and their related + parameters (e.g., niceness, priority, runtime/deadline/period). rt-app + is a valuable tool, as it can be used to synthetically recreate certain + workloads (maybe mimicking real use-cases) and evaluate how the scheduler + behaves under such workloads. In this way, results are easily reproducible. + rt-app is available at: https://github.com/scheduler-tools/rt-app. + + Threads parameters can be specified from command line, with something like + this: + + # rt-app -t 100000:10000:d -t 150000:20000:f:10 -D5 + + What above creates two threads, first one, scheduled by SCHED_DEADLINE, + executes for 10ms every 100ms and second one, scheduled at RT priority 10 + with SCHED_FIFO, executes for 20ms every 150ms. The configuration runs + for 5 seconds. + + More interestingly, configurations can be described with a json file, that + can be passed as input to rt-app with something like this: + + # rt-app my_config.json + + The parameters that can be specified with the second method are a superset + of the command line options. Please refer to rt-app documentation for more + details. + + The second testing application is a modification of schedtool, called + schedtool-dl, which can be used to setup SCHED_DEADLINE parameters for a + certain pid/application. schedtool-dl is available at: + https://github.com/scheduler-tools/schedtool-dl.git. + + The usage is straightforward: + + # schedtool -E -t 10000000:100000000 -e ./my_cpuhog_app + + With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation + of 10ms every 100ms (note that parameters are expressed in microseconds). + You can also use schedtool to create a reservation for an already running + application, given that you know its pid: + + # schedtool -E -t 10000000:100000000 my_app_pid -- 1.7.9.5