Received: by 10.192.165.148 with SMTP id m20csp2270541imm; Thu, 3 May 2018 13:25:34 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqAK0oakSnpAxtuzwA3B2yyywC1sUSkYSPGhOVvZ8y2MtGo+PtwDbIEPHbiC5pXCEPrpFq7 X-Received: by 2002:a17:902:9a0c:: with SMTP id v12-v6mr24553523plp.162.1525379134659; Thu, 03 May 2018 13:25:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525379134; cv=none; d=google.com; s=arc-20160816; b=U0aNuzz85OtSNe//EJ1/WIbv3uvbvyRFj1GvY+nvR8N+M18Yxn7LCSqEgZseq6Rl5N CRQdHg5HS4rCWaptgc7yc3meyayU53E6UD+7o/t4S3A6JmZPKeEtMfnu9jdkAYzv42RK esnsnoIBpsj/zvXkBtnLApk8K6kId2V9lFLRAYr1Pn6RUfPPXLSMNvjPWUamESyRbWfO EGAuD8rDL5NEOz9di6e3t6QAAY0Pez85YgDWgH/6EccKxa4znTK9Kwq2/05QFauhy67e wGBY4LELgcfaI0yI1AwVn+f8pX68Li9v4j2qO/XIs1SJ49Il7xE69rt6hWCWGeHaJg4z fHTQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=fsFGQKTQkPISdjOMeCvc8YFexVB/neJWV1bhG7AQKF4=; b=Ko66+WYrDAeZXUlldPlMTp4xqBZ++R/TwUeh81Savs5nCmplYH8lNZmL88akbLqt7J c05Fs3w+3zT2XYoHyeCzp0mf8ei4oqv+sctlklZ0DzwND95pa6wil/w7L20q2MywyZXl 3tbNbBWhFrEA2mUMd2BIHlm9Z8lusmLo1lophfgjbG5zCMUtbpOYl9A+fu1sjyswBfcY m6sVlDMG2UY/ZEyzKdJz+aOHa4fEIlKpRGUPROzOo8Guv/b9Ofrk0rRS1u1BpkumbuFJ 9IQkPLhuKvepIvOaT5WopPX+w7RWyWvPF3jBRnl7w75s0SC1YdRrb941Cwrz0hwVY/7a /feQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=LKcTLFZN; 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 q2-v6si14094336plh.259.2018.05.03.13.25.20; Thu, 03 May 2018 13:25:34 -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; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=LKcTLFZN; 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 S1751412AbeECUZE (ORCPT + 99 others); Thu, 3 May 2018 16:25:04 -0400 Received: from mail-io0-f194.google.com ([209.85.223.194]:45114 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751354AbeECUZB (ORCPT ); Thu, 3 May 2018 16:25:01 -0400 Received: by mail-io0-f194.google.com with SMTP id c9-v6so16815270iob.12 for ; Thu, 03 May 2018 13:25:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=fsFGQKTQkPISdjOMeCvc8YFexVB/neJWV1bhG7AQKF4=; b=LKcTLFZN44y56cZlK5Kzdy5jNvC1rx9uEb+1dXPKFpK6ElQ0xOxAjDYHO2bRBb+OcV YZgK21d6Z16PHFoqubs6n1MejChO+2dAfGzzCdwUHdWErJXjCg/jQLAlj6iBJ02ueFG9 Sto4PaDAwB04kLVKF5EUVPWonOPT48mXz8/f4yE1fYpvq36xqGfU8YhbQ16Ds/1dfveD Uizx4ek1YRiHGL6EySUZyE744vRXG1nFiS9mASNs2deR/yQ+RrCb8H1QCFv6uqRcejc+ 6h6MYQhkfsoce8Qxih/hYigIVDulNyzXWCXj6ZEdBZQltBELLg95UX+46rF54OjDV2Qg hpZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fsFGQKTQkPISdjOMeCvc8YFexVB/neJWV1bhG7AQKF4=; b=uVAFdzTV3oLxIWBfkhDLlYi9iN5WWt8RdntHnt6JWAWsm9SN9KIygWqeGVX6CjQLIE QkbeQ+8Gtty7BWV+kTTYjbKuXNAJs3BqWLUmUjB1fLdTDF92dzuq0Ej9bTxaTPxaSw+Z iMA+HqpKj4iP6UNRf2ThGfnnInLuEvSCwgn87GKgnJs1JJizeEQD/HKrMzXRHLJJnbTr Qe9h1mnISi6+ykxTYh8qJ1KhQgiIe60MUQfcX4Ky987QTywX3MTgSw9YR0YNAZPd5Gug ZkQXT/Us4NZukEBQ4fTksly575gcEMQp4RZsKpRtpJ7pCNVz/9pWBGBu7u7N2FBHBbYQ bSRQ== X-Gm-Message-State: ALQs6tDwwocXiEraZdkntXiGd0So0FeHTrALH9ySyHzIIk7CVvkDmdsj RVeTGASzBeAEGIHjX7yawz6LXsXAENA= X-Received: by 2002:a6b:250d:: with SMTP id l13-v6mr25575700iol.47.1525379100562; Thu, 03 May 2018 13:25:00 -0700 (PDT) Received: from [192.168.1.168] ([216.160.245.98]) by smtp.gmail.com with ESMTPSA id d143-v6sm189972itd.35.2018.05.03.13.24.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 May 2018 13:24:59 -0700 (PDT) Subject: Re: [PATCH v2] fs: Add aio iopriority support for block_dev To: Adam Manzanares , Matthew Wilcox 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" References: <20180503182114.2797-1-adam.manzanares@wdc.com> <20180503183353.GC1562@bombadil.infradead.org> <47e0a519-37b4-f5e7-0616-8659d11c2b69@wdc.com> From: Jens Axboe Message-ID: <18300bdb-a12f-0b6c-1317-6db3e4391d57@kernel.dk> Date: Thu, 3 May 2018 14:24:58 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <47e0a519-37b4-f5e7-0616-8659d11c2b69@wdc.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/3/18 2:15 PM, Adam Manzanares wrote: > > > On 5/3/18 11:33 AM, Matthew Wilcox wrote: >> On Thu, May 03, 2018 at 11:21:14AM -0700, adam.manzanares@wdc.com wrote: >>> 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. >> >> Or we could just make ki_hint a u8 or u16 ... seems unlikely we'll need >> 32 bits of ki_hint. (currently defined values are 1-5) > > I like the approach of using a u16 for the ki_hint. I'll update and > resubmit. It's intended to be a mask. If you do shrink it for now, then we need some guard code to ensure it can always carry what it needs to. -- Jens Axboe