Received: by 10.192.165.148 with SMTP id m20csp2173704imm; Thu, 3 May 2018 11:36:47 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpr4lcxwihsYe5EjSSVrT2YhzIOzQtjs22ogHntK8+tJU9HqF+czjZr1v7ElLfknWTTuxAi X-Received: by 10.167.128.82 with SMTP id y18mr23679549pfm.194.1525372607779; Thu, 03 May 2018 11:36:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525372607; cv=none; d=google.com; s=arc-20160816; b=zzx778cJiOIHBH+qSZuQpQjAOHn0NvwR6vhxRSRyyKAldsdc3fxUoGgy4FE6KI0QsS cfWQyPgwGYlx2rnd0H/HxFEB9s8LRjTBfYU7GblsqdaK9KS4stWoIzYxYinCu4F2nHs3 BQubRQNSu3f5Q+IfR3LmkU06HRbOovlBFDKTRWCOoglYX9kNUNhlK8wvFfi6yfrqmYuN K12OQPwW3Lt0gTeZznO16qZUnT2RWYD8vkxWyAIMsccDG9UgdhE0ltcLjQ8Dw6Y7PExe x1H7AlkyRUHQ5Q/SIA1SraOSyMffTN4u9GfWm41yoQoOkYnxhYRdjEi8bolB8DpbbbpY pBaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from :arc-authentication-results; bh=M21L/e3SL2NK7G+tQRp43JpADzoTqRKuqklMWUVHcjA=; b=DB3i4QBFnBLYC9xfYqK/EyCKJ1P23/G7TSDfE8glxaQYLuC0zHeMl4wk3ZXUMh3d1K 4EjDirvnLaYq73pG8g7fw9c38TEW6v0/nBVXPlIUm0pFbHwQbpUd6P2yrKuVVAazoJdZ fsxdQQMlhHELfFa/jnYCiWhwit9lNgpfoD2BwPOe0/ytKVzKC/ndBFmhmt/AnhH/+oaE FA4YZ8MXtjCjnItyIIkFNeYSfkztsgTj5KddsiVb4/+IScVC3+jiKIzNkCpdSX94/KvD 8RHvgv0GEMj+Op2Z721KPX3ofYiqsQ/kFOs90s5Yp96tGgwz8Gg1q/+cbvj4DXB9K5n5 HeeA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g1-v6si5697254pld.11.2018.05.03.11.36.33; Thu, 03 May 2018 11:36:47 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751272AbeECSgT (ORCPT + 99 others); Thu, 3 May 2018 14:36:19 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:45316 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750969AbeECSgR (ORCPT ); Thu, 3 May 2018 14:36:17 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8EDEB7CBBA; Thu, 3 May 2018 18:36:16 +0000 (UTC) Received: from segfault.boston.devel.redhat.com (segfault.boston.devel.redhat.com [10.19.60.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E33F111166E0; Thu, 3 May 2018 18:36:15 +0000 (UTC) From: Jeff Moyer To: adam.manzanares@wdc.com Cc: viro@zeniv.linux.org.uk, bcrl@kvack.org, linux-fsdevel@vger.kernel.org, linux-aio@kvack.org, linux-api@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] fs: Add aio iopriority support for block_dev References: <20180503182114.2797-1-adam.manzanares@wdc.com> X-PGP-KeyID: 1F78E1B4 X-PGP-CertKey: F6FE 280D 8293 F72C 65FD 5A58 1FF8 A7CA 1F78 E1B4 X-PCLoadLetter: What the f**k does that mean? Date: Thu, 03 May 2018 14:36:15 -0400 In-Reply-To: <20180503182114.2797-1-adam.manzanares@wdc.com> (adam manzanares's message of "Thu, 3 May 2018 11:21:14 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Thu, 03 May 2018 18:36:16 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Thu, 03 May 2018 18:36:16 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'jmoyer@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Adam, adam.manzanares@wdc.com writes: > From: Adam Manzanares > > This is the per-I/O equivalent of the ioprio_set system call. > > When IOCB_FLAG_IOPRIO is set on the iocb aio_flags field, then we set the > newly added kiocb ki_ioprio field to the value in the iocb aio_reqprio field. > > When a bio is created for an aio request by the block dev we set the priority > value of the bio to the user supplied value. > > See the following link for performance implications on a SATA HDD: > https://lkml.org/lkml/2016/12/6/495 > > Given that WRR support for NVME devices has patches floating around and it was > discussed at LSFMM, we may soon have a lower latency storage device that can > make use of iopriorities. A per command iopriority interface seems timely > given these developments. > > If we want to avoid bloating struct kiocb, I suggest we turn the private field > into a union of the private and ki_ioprio field. It seems like the users of > the private field all use it at a point where we can yank the priority from > the kiocb before the private field is used. Comments and suggestions welcome. The ioprio_set system call requires CAP_SYS_ADMIN for setting IOPRIO_CLASS_RT. I think we need similar checks here. -Jeff > > v2: merge patches > use IOCB_FLAG_IOPRIO > validate intended use with IOCB_IOPRIO > add linux-api and linux-block to cc > > Signed-off-by: Adam Manzanares > --- > fs/aio.c | 10 ++++++++++ > fs/block_dev.c | 2 ++ > include/linux/fs.h | 2 ++ > include/uapi/linux/aio_abi.h | 1 + > 4 files changed, 15 insertions(+) > > diff --git a/fs/aio.c b/fs/aio.c > index 88d7927ffbc6..f36636d8ff2c 100644 > --- a/fs/aio.c > +++ b/fs/aio.c > @@ -1597,6 +1597,16 @@ static int io_submit_one(struct kioctx *ctx, struct iocb __user *user_iocb, > req->common.ki_flags |= IOCB_EVENTFD; > } > > + if (iocb->aio_flags & IOCB_FLAG_IOPRIO) { > + /* > + * If the IOCB_FLAG_IOPRIO flag of aio_flags is set, then > + * aio_reqprio is interpreted as an I/O scheduling > + * class and priority. > + */ > + req->common.ki_ioprio = iocb->aio_reqprio; > + req->common.ki_flags |= IOCB_IOPRIO; > + } > + > ret = kiocb_set_rw_flags(&req->common, iocb->aio_rw_flags); > if (unlikely(ret)) { > pr_debug("EINVAL: aio_rw_flags\n"); > diff --git a/fs/block_dev.c b/fs/block_dev.c > index 7ec920e27065..970bef79caa6 100644 > --- a/fs/block_dev.c > +++ b/fs/block_dev.c > @@ -355,6 +355,8 @@ __blkdev_direct_IO(struct kiocb *iocb, struct iov_iter *iter, int nr_pages) > bio->bi_write_hint = iocb->ki_hint; > bio->bi_private = dio; > bio->bi_end_io = blkdev_bio_end_io; > + if (iocb->ki_flags & IOCB_IOPRIO) > + bio->bi_ioprio = iocb->ki_ioprio; > > ret = bio_iov_iter_get_pages(bio, iter); > if (unlikely(ret)) { > diff --git a/include/linux/fs.h b/include/linux/fs.h > index 760d8da1b6c7..ab63ce720305 100644 > --- a/include/linux/fs.h > +++ b/include/linux/fs.h > @@ -292,6 +292,7 @@ enum rw_hint { > #define IOCB_SYNC (1 << 5) > #define IOCB_WRITE (1 << 6) > #define IOCB_NOWAIT (1 << 7) > +#define IOCB_IOPRIO (1 << 8) > > struct kiocb { > struct file *ki_filp; > @@ -300,6 +301,7 @@ struct kiocb { > void *private; > int ki_flags; > enum rw_hint ki_hint; > + u16 ki_ioprio; /* See linux/ioprio.h */ > } __randomize_layout; > > static inline bool is_sync_kiocb(struct kiocb *kiocb) > diff --git a/include/uapi/linux/aio_abi.h b/include/uapi/linux/aio_abi.h > index a04adbc70ddf..d4593a6062ef 100644 > --- a/include/uapi/linux/aio_abi.h > +++ b/include/uapi/linux/aio_abi.h > @@ -54,6 +54,7 @@ enum { > * is valid. > */ > #define IOCB_FLAG_RESFD (1 << 0) > +#define IOCB_FLAG_IOPRIO (1 << 1) > > /* read() from /dev/aio returns these structures. */ > struct io_event {