Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp375499imu; Thu, 8 Nov 2018 09:27:50 -0800 (PST) X-Google-Smtp-Source: AJdET5cgJcjsk17pHdMcK3Mx70IptWWbsXsVWXth1yt8plrTIY2uKi3r9C7ySDx1063eREOGM8kZ X-Received: by 2002:a17:902:bccc:: with SMTP id o12-v6mr5476442pls.281.1541698070175; Thu, 08 Nov 2018 09:27:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541698070; cv=none; d=google.com; s=arc-20160816; b=B1f50tsmvjnMVM3/0JwlWHCSuY6e9RkNUlOMbNr5hguL86+xa2IbtYsPZ8XzH8Hwpf 4+mjNcg2eZ4LHsg1dw6rfKvwAhDvzq0dJWfjDbLMhdpONKNdIQUFORbRh2Sk/98ys062 MusLg9z+62YaAkkyAjOgwiED9yqWD6JUpfvGwhRDDK/WCndOqC8CNUfyfgr5w50KQM1l rHhJ0g2YM6u99YrI0kpBgmItw6vfOZ+hbzxdohli9a2iUUowRUu6U7VggUnVpGcRHIzj gzU+laXZGIhiwGnLm4NbALHNgEV/kQswvOeCueLselB4vcZLGDMmuN6w0aBfL0ruyLko EaYA== 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=sKQz2kOe2xWzmDXdBd7qSFLioHLqlYGow1r1w59wS7w=; b=hHHl/D2L2VaKeS5J4efA3Rc7O1WczbPEi0gjMWChwXDsN3qK9j83VNgbvAjAEF19ms SmE29XTzPoh2apvlzgYsv1eibPz29vHvVYXsv9UfqFs3jvNzUXOuCRiPYcfiJZN6RBqY 3hK40oW8lkZV2vm2mgggNwGIGbSinPdroBowNImpm/UXiwg/1xsuN2RuARn6I47kqMlY 5JuTsGVVG5TyuUZu890Bp77se11elkCgjEvdXF3zz5QaRZeLCDIIyoZRzK009qmSHfqo 0FK8g3q1Fbzqf3WhWY+mGaZJ9AktO0e6UdcVYZ5q0dWpnuXCwZJ0Q6t+4i5VzccwMQTE 38rw== 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 199-v6si4879980pfu.273.2018.11.08.09.27.31; Thu, 08 Nov 2018 09:27:50 -0800 (PST) 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 S1727266AbeKIDDK (ORCPT + 99 others); Thu, 8 Nov 2018 22:03:10 -0500 Received: from ms.lwn.net ([45.79.88.28]:59658 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726583AbeKIDDK (ORCPT ); Thu, 8 Nov 2018 22:03:10 -0500 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 3B59C4FA; Thu, 8 Nov 2018 17:26:39 +0000 (UTC) Date: Thu, 8 Nov 2018 10:26:38 -0700 From: Jonathan Corbet To: Daniel Jordan Cc: linux-mm@kvack.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, aarcange@redhat.com, aaron.lu@intel.com, akpm@linux-foundation.org, alex.williamson@redhat.com, bsd@redhat.com, darrick.wong@oracle.com, dave.hansen@linux.intel.com, jgg@mellanox.com, jwadams@google.com, jiangshanlai@gmail.com, mhocko@kernel.org, mike.kravetz@oracle.com, Pavel.Tatashin@microsoft.com, prasad.singamsetty@oracle.com, rdunlap@infradead.org, steven.sistare@oracle.com, tim.c.chen@intel.com, tj@kernel.org, vbabka@suse.cz Subject: Re: [RFC PATCH v4 01/13] ktask: add documentation Message-ID: <20181108102638.3415ae0b@lwn.net> In-Reply-To: <20181105165558.11698-2-daniel.m.jordan@oracle.com> References: <20181105165558.11698-1-daniel.m.jordan@oracle.com> <20181105165558.11698-2-daniel.m.jordan@oracle.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 Mon, 5 Nov 2018 11:55:46 -0500 Daniel Jordan wrote: > Motivates and explains the ktask API for kernel clients. A couple of quick thoughts: - Agree with Peter on the use of "task"; something like "job" would be far less likely to create confusion. Maybe you could even call it a "batch job" to give us old-timers warm fuzzies...:) - You have kerneldoc comments for the API functions, but you don't pull those into the documentation itself. Adding some kernel-doc directives could help to fill things out nicely with little effort. Thanks, jon