[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180502173207.GA27997@infradead.org>
Date: Wed, 2 May 2018 10:32:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: adam.manzanares@....com
Cc: viro@...iv.linux.org.uk, bcrl@...ck.org,
linux-fsdevel@...r.kernel.org, linux-aio@...ck.org,
linux-abi-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] fs: add RWF_IOPRIO
On Mon, Apr 30, 2018 at 09:57:39AM -0700, adam.manzanares@....com wrote:
> From: Adam Manzanares <adam.manzanares@....com>
>
> This is the per-I/O equivalent of the ioprio_set system call.
>
> When the RWF_IOPRIO flag is set then the aio_reqprio field of the iocb
> is interpreted as an I/O scheduling class and priority.
I think this belongs into the IOCB_FLAG_* flags namespace for aio_flags
field as it isn't a field valid for plain read/write.
Also you probably want to merge both patches as they only really
make sense together.
Powered by blists - more mailing lists