[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49fu2kvi9q.fsf@segfault.boston.devel.redhat.com>
Date: Mon, 21 May 2018 16:57:37 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: adam.manzanares@....com
Cc: viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
axboe@...nel.dk, bcrl@...ck.org, tglx@...utronix.de,
mingo@...nel.org, pombredanne@...b.com,
kstewart@...uxfoundation.org, gregkh@...uxfoundation.org,
bigeasy@...utronix.de, jack@...e.cz, darrick.wong@...cle.com,
rgoldwyn@...e.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-aio@...ck.org,
linux-api@...r.kernel.org, hch@...radead.org
Subject: Re: [PATCH v5 0/5] AIO add per-command iopriority
Hi, Adam,
adam.manzanares@....com writes:
> From: Adam Manzanares <adam.manzanares@....com>
>
> This is the per-I/O equivalent of the ioprio_set system call.
> See the following link for performance implications on a SATA HDD:
> https://lkml.org/lkml/2016/12/6/495
>
> First patch factors ioprio_check_cap function out of ioprio_set system call to
> also be used by the aio ioprio interface.
>
> Second patch converts kiocb ki_hint field to a u16 to avoid kiocb bloat.
>
> Third patch passes ioprio hint from aio iocb to kiocb and inititalizes kiocb
> ioprio value appropriately when it is not explicitly set.
>
> Fourth patch enables the feature for blkdev.
>
> Fifth patch enables the feature for iomap direct IO
>
> Note: this work is based on top of linux-vfs/for-next
I'll cook up a libaio test case. Can you put together a man-pages
update for this?
Thanks!
Jeff
Powered by blists - more mailing lists