Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4702773ybb; Tue, 7 Apr 2020 12:41:42 -0700 (PDT) X-Google-Smtp-Source: APiQypLfOj3DYtSJIjnb0xnXfA1V23431mvfd0Pz6waY3cW/4oHFJUGMsdH1mBce3Vl7NgcnhV8A X-Received: by 2002:a05:6830:4008:: with SMTP id h8mr3074257ots.295.1586288501912; Tue, 07 Apr 2020 12:41:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586288501; cv=none; d=google.com; s=arc-20160816; b=WvIFfVoUPg6CD/AGTxDyxlVl/YHJKGQLN558/DHMZGiDUwhItt3iWiRpVIWVcbEQ1I ln/q2G1GaSetBijNWSUpWdo4mmPc7Lm4m1L/WBGmsF42ecMu0rxHwl4WaNJQfQO5w6/2 p43aauTM95oL8QVYu9wMbKoLbKRNuO9oB8aHU//3qyDY7KDq1iW2dVnqG04F894Rq+Cz C0ONzxRJzIsRAzrGJxSdJs9HcFE0VNWVoraEZl7SCbHj9RrcrL9nJqOXWBqgREMRe78v /Sg4j05a5c15B+P1DH6J5pcrUgnrcGYeJI9zV9OKiBDunJshUVNHZy2xsPdY4LFAUr5X DBcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=bUyJrZlfMKEuQUOkaDpp4vJXA5l1j7A+VQJ2TO4t6pI=; b=otxLRO1msYmdT87ka0KwunSyNRc8y+XVTq0WVmRXzNfa1hkiyxXF0CPhzihrtbAzAc GHlsVGZFJMsB+lZ3qpAQooB2gzm7DiqInOrumJ7pmUVLqChoF/h8Son2fIZXS8c6BQG3 sio9cEm4RHV7zlVFSeQdkCbhg9LjgyZ2FY8BwuvTXlsiwOufAI8GF/Um1WKVGmcObSaA hwhYmb8fq+lD2ElUxGoV1TzEqZO1iT6Ubl88id4fKyNdxLWDUtDG2L1zvuEKye9M4VYM O8YQd4mTognffjpK1OQwCYV9iG7BrS/Ggr704LAE8OZ1ufaMuekXtWeY1u86dP64Y9YD r7OQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w5si1542892ote.129.2020.04.07.12.41.26; Tue, 07 Apr 2020 12:41:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726883AbgDGTkb (ORCPT + 99 others); Tue, 7 Apr 2020 15:40:31 -0400 Received: from ms.lwn.net ([45.79.88.28]:40610 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726719AbgDGTkb (ORCPT ); Tue, 7 Apr 2020 15:40:31 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 82BD260C; Tue, 7 Apr 2020 19:40:29 +0000 (UTC) Date: Tue, 7 Apr 2020 13:40:28 -0600 From: Jonathan Corbet To: Daniel Bristot de Oliveira Cc: Peter Zijlstra , John Mathew , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, tsbogend@alpha.franken.de, lukas.bulwahn@gmail.com, x86@kernel.org, linux-mips@vger.kernel.org, tglx@linutronix.de, mostafa.chamanara@basemark.com Subject: Re: [RFC PATCH 2/3] docs: scheduler: Add scheduler overview documentation Message-ID: <20200407134028.44d0d16a@lwn.net> In-Reply-To: <9614b346-a848-3e01-eea7-6237b759dad6@redhat.com> References: <20200401100029.1445-1-john.mathew@unikie.com> <20200401100029.1445-3-john.mathew@unikie.com> <20200401103520.GA20713@hirez.programming.kicks-ass.net> <9614b346-a848-3e01-eea7-6237b759dad6@redhat.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 1 Apr 2020 13:47:04 +0200 Daniel Bristot de Oliveira wrote: > > And that is a prime example of why I hates RST, it pretty much mandates > > you view this with something other than a text editor. > > The good thing about the dot format is that we can convert it to many other > formats, including text: > > [bristot@x1 ~]$ cat sched_transition.dot | graph-easy > > * > > | > | task > | forks > v > +------------------------------------+ > | TASK_NEW | > | (Ready to run) | > +------------------------------------+ > | > | > v > + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+ > ' int ' > ' ' > ' +------------------------------------+ ' > ' | TASK_RUNNING | ' > ' +--------------> | (Ready to run) | <--+ ' > ' | +------------------------------------+ | ' > ' | | | ' > ' | | schedule() calls context_switch() | task is pre-empted ' > ' | v | ' > ' | +------------------------------------+ | ' > ' | | TASK_RUNNING | | ' > ' | | (Running) | ---+ ' > ' | event occurred +------------------------------------+ ' > ' | | ' > ' | | - - - - - - - - - - - -+ > ' | | ' > ' | | task needs to wait for event ' > ' | v ' > ' | +------------------------------------+ ' > ' | | TASK_INTERRUPTIBLE | ' > ' | | TASK_UNINTERRUPTIBLE | ' > ' +--------------- | TASK_WAKEKILL | ' > ' +------------------------------------+ ' > ' ' > + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + > | > | task exits via do_exit() > v > +------------------------------------+ > | TASK_DEAD | > | EXIT_ZOMBIE | > +------------------------------------+ > > > Is there a way to also add this representation, while hiding it > when using a graphical reader? Better, honestly, to just put the ascii art into the doc as a literal block. I don't see any real reason to embed Dot stuff unless there's really no alternative. Thanks, jon