From: Jeff Moyer <jmoyer@redhat.com>
To: "Jason B. Akers" <jason.b.akers@intel.com>
Cc: linux-ide@vger.kernel.org, axboe@fb.com, kapil.karkra@intel.com,
dan.j.williams@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] block, ioprio: include caching advice via ionice
Date: Wed, 29 Oct 2014 15:02:42 -0400 [thread overview]
Message-ID: <x49bnoupulp.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20141029182345.4879.98373.stgit@stg-AndroidDev-VirtualBox> (Jason B. Akers's message of "Wed, 29 Oct 2014 11:23:45 -0700")
"Jason B. Akers" <jason.b.akers@intel.com> writes:
> From: Dan Williams <dan.j.williams@intel.com>
>
> Steal one unused bit from the priority class and two bits from the
> priority data, to implement a 3 bit cache-advice field. Similar to the
> page cache advice from fadvise() these hints are meant to be consumed
> by hybrid drives. Solid State Hyrbid-Drives, as defined by the SATA-IO
> Specification, implement up to a 4-bit cache priority that can be
> specified along with a FPDMA command.
ionice is about setting an I/O scheduling class for a *process*. So,
unless I've missed something, this does not seem like the right
interface for passing I/O hints.
You mention fadvise hints, which sounds like a good fit (and madvise
would be equally interesting), but I don't see where you've wired them
up in this patch set. Did I miss it?
Cheers,
Jeff
next prev parent reply other threads:[~2014-10-29 19:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:23 [RFC PATCH 0/5] Enable use of Solid State Hybrid Drives Jason B. Akers
2014-10-29 18:23 ` [RFC PATCH 1/5] block, ioprio: include caching advice via ionice Jason B. Akers
2014-10-29 19:02 ` Jeff Moyer [this message]
2014-10-29 21:07 ` Dan Williams
2014-10-29 18:23 ` [RFC PATCH 2/5] block: ioprio hint to low-level device drivers Jason B. Akers
2014-10-29 18:23 ` [RFC PATCH 3/5] block: untangle ioprio from BLK_CGROUP and BLK_DEV_THROTTLING Jason B. Akers
2014-10-29 18:24 ` [RFC PATCH 4/5] block, mm: Added the necessary plumbing to take ioprio hints down to block layer Jason B. Akers
2014-10-29 18:24 ` [RFC PATCH 5/5] libata: Enabling Solid State Hybrid Drives (SSHDs) based on SATA 3.2 standard Jason B. Akers
2014-10-29 20:14 ` [RFC PATCH 0/5] Enable use of Solid State Hybrid Drives Dave Chinner
2014-10-29 21:10 ` Jens Axboe
2014-10-29 22:09 ` Dave Chinner
2014-10-29 22:24 ` Dan Williams
2014-10-30 7:21 ` Dave Chinner
2014-10-30 14:15 ` Jens Axboe
2014-10-30 17:07 ` Dan Williams
2014-11-10 4:22 ` Dave Chinner
2014-11-12 16:47 ` Dan Williams
2014-10-29 22:49 ` Jens Axboe
2014-10-29 21:11 ` Dan Williams
2014-12-03 15:25 ` Pavel Machek
2014-10-30 2:05 ` Martin K. Petersen
2014-10-30 2:35 ` Jens Axboe
2014-10-30 3:28 ` Martin K. Petersen
2014-10-30 4:19 ` Dan Williams
2014-10-30 14:17 ` Jens Axboe
2014-10-30 14:53 ` Jens Axboe
2014-10-30 16:27 ` Dan Williams
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=x49bnoupulp.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=jason.b.akers@intel.com \
--cc=kapil.karkra@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).