From: Jens Axboe <axboe@suse.de>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel@kolivas.org, nickpiggin@yahoo.com.au
Subject: Re: IO Priorities
Date: Mon, 13 Dec 2004 17:46:25 +0100 [thread overview]
Message-ID: <20041213164625.GX3033@suse.de> (raw)
In-Reply-To: <20041213164325.GA26031@optonline.net>
On Mon, Dec 13 2004, Jeff Sipek wrote:
> On Mon, Dec 13, 2004 at 03:38:10PM +0100, Jens Axboe wrote:
> > On Mon, Dec 13 2004, Jeff Sipek wrote:
> > > Hello all,
> > > About a week ago, I said I would try to implement IO priorities.
> > > I tried. I got the whole thing done, but there is one major problem - it
> >
> > I did too, did you see my patch?
>
> I did after I sent mine. I was reading it and I noticed:
>
> "Disable TCQ in the hardware/driver by default. Can be changed (as
> always) with the max_depth setting. If you do that, don't expect
> fairness or priorities to work as well."
>
> Would this cause my problem?
Only if you test on SCSI with TCQ enabled. But I already outlined what
your problems are even if you did.
> > Additionally, you don't do anything with the priorities internally.
>
> Sure I do, I multiply the slice by cfq_prio_scale[ioprio]. It did seem
> too simple. :-) Looking at your code right now, I kind of see some code
> that should have been in my implementation as well. Back to coding...
> :-)
If you would base changes on what I already did with CFQ, that would be
handy. You need the CFQ bits anyways.
Updated patch here:
http://www.kernel.org/pub/linux/kernel/people/axboe/patches/v2.6/2.6.10-rc3-mm1/cfq-time-slices-11-2.6.10-rc3-mm1.gz
--
Jens Axboe
prev parent reply other threads:[~2004-12-13 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 14:22 IO Priorities Jeff Sipek
2004-12-13 14:38 ` Jens Axboe
2004-12-13 16:43 ` Jeff Sipek
2004-12-13 16:46 ` Jens Axboe [this message]
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=20041213164625.GX3033@suse.de \
--to=axboe@suse.de \
--cc=jeffpc@optonline.net \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.