From: Jens Axboe <jens.axboe@oracle.com>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
?????? ?????? <yoshikawa.takuya@oss.ntt.co.jp>,
dpshah@google.com
Subject: Re: [PATCH] virtio_blk: use a wrapper function to access io context information of IO requests
Date: Thu, 14 Aug 2008 09:58:03 +0200 [thread overview]
Message-ID: <20080814075802.GI20055@kernel.dk> (raw)
In-Reply-To: <1218691323.31285.31.camel@sebastian.kern.oss.ntt.co.jp>
On Thu, Aug 14 2008, Fernando Luis Vázquez Cao wrote:
> struct request has an ioprio member but it is never updated because
> currently bios do not hold io context information. The implication of
> this is that virtio_blk ends up passing useless information to the
> backend driver.
>
> That said, some IO schedulers such as CFQ do store io context
> information in struct request, but use private members for that, which
> means that that information cannot be directly accessed in a IO
> scheduler-independent way.
>
> This patch adds a function to obtain the ioprio of a request. We should
> avoid accessing ioprio directly and use this function instead, so that
> its users do not have to care about future changes in block layer
> structures or what the currently active IO controller is.
>
> This patch does not introduce any functional changes but paves the way
> for future clean-ups and enhancements.
>
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Fine with me, applied.
--
Jens Axboe
next prev parent reply other threads:[~2008-08-14 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1218014196.4419.44.camel@sebastian.kern.oss.ntt.co.jp>
2008-08-06 20:33 ` request->ioprio Rusty Russell
2008-08-13 7:06 ` request->ioprio Fernando Luis Vázquez Cao
2008-08-13 8:14 ` [PATCH] virtio_blk: use a wrapper function to access io context information of IO requests Fernando Luis Vázquez Cao
2008-08-14 4:42 ` Rusty Russell
2008-08-14 5:17 ` Fernando Luis Vázquez Cao
2008-08-14 5:22 ` Fernando Luis Vázquez Cao
2008-08-14 7:58 ` Jens Axboe [this message]
2008-08-14 2:16 ` request->ioprio Rusty Russell
2008-08-14 4:26 ` request->ioprio Fernando Luis Vázquez Cao
2008-08-15 5:51 ` request->ioprio Fernando Luis Vázquez Cao
2008-08-16 7:13 ` request->ioprio Rusty Russell
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=20080814075802.GI20055@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dpshah@google.com \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.