From: Tejun Heo <tj@kernel.org>
To: Adam Manzanares <adam.manzanares@hgst.com>
Cc: axboe@kernel.dk, dan.j.williams@intel.com, hare@suse.de,
martin.petersen@oracle.com, mchristi@redhat.com,
toshi.kani@hpe.com, ming.lei@canonical.com,
sathya.prakash@broadcom.com, chaitra.basappa@broadcom.com,
suganath-prabu.subramani@broadcom.com,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, MPT-FusionLinux.pdl@broadcom.com,
linux-scsi@vger.kernel.org,
Adam Manzananares <adam.manzanares@wdc.com>
Subject: Re: [PATCH v6 1/3] block: Add iocontext priority to request
Date: Wed, 19 Oct 2016 14:05:24 -0400 [thread overview]
Message-ID: <20161019180524.GH18532@htj.duckdns.org> (raw)
In-Reply-To: <1476728850-2309-2-git-send-email-adam.manzanares@hgst.com>
Hello,
On Mon, Oct 17, 2016 at 11:27:28AM -0700, Adam Manzanares wrote:
> Patch adds an association between iocontext ioprio and the ioprio of a
> request. This is done to enable request based drivers the ability to
> act on priority information stored in the request. An example being
> ATA devices that support command priorities. If the ATA driver discovers
> that the device supports command priorities and the request has valid
> priority information indicating the request is high priority, then a high
> priority command can be sent to the device. This should improve tail
> latencies for high priority IO on any device that queues requests
> internally and can make use of the priority information stored in the
> request.
>
> The ioprio of the request is set in blk_rq_set_prio which takes the
> request and the ioc as arguments. If the ioc is valid in blk_rq_set_prio
> then the iopriority of the request is set as the iopriority of the ioc.
> In init_request_from_bio a check is made to see if the ioprio of the bio
> is valid and if so then the request prio comes from the bio.
>
> Signed-off-by: Adam Manzananares <adam.manzanares@wdc.com>
Jens, if you're okay with it, I can route this through
libata/for-4.10, or this can be applied to block and libata tree can
pull from it.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-10-19 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:27 [PATCH v6 0/3] Enabling ATA Command Priorities Adam Manzanares
2016-10-17 18:27 ` [PATCH v6 1/3] block: Add iocontext priority to request Adam Manzanares
2016-10-19 18:05 ` Tejun Heo [this message]
2016-10-19 18:08 ` Jens Axboe
2016-10-17 18:27 ` [PATCH v6 2/3] ata: Enabling ATA Command Priorities Adam Manzanares
2016-10-19 18:37 ` Tejun Heo
2016-10-17 18:27 ` [PATCH v6 3/3] ata: ATA Command Priority Disabled By Default Adam Manzanares
2016-10-19 18:05 ` Tejun Heo
2016-10-19 18:09 ` Adam Manzanares
2016-10-19 18:38 ` Tejun Heo
2016-10-19 20:02 ` Adam Manzanares
2016-10-19 18:38 ` [PATCH v6 0/3] Enabling ATA Command Priorities Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161019180524.GH18532@htj.duckdns.org \
--to=tj@kernel.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=adam.manzanares@hgst.com \
--cc=adam.manzanares@wdc.com \
--cc=axboe@kernel.dk \
--cc=chaitra.basappa@broadcom.com \
--cc=dan.j.williams@intel.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchristi@redhat.com \
--cc=ming.lei@canonical.com \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=toshi.kani@hpe.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).