All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Jens Axboe <axboe@suse.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: elevator priorities vs. full request queues
Date: Mon, 12 Jul 2004 20:52:27 -0300	[thread overview]
Message-ID: <20040712205227.A12285@almesberger.net> (raw)
In-Reply-To: <20040623101430.GI1120@suse.de>; from axboe@suse.de on Wed, Jun 23, 2004 at 12:14:31PM +0200

Jens Axboe wrote:
> Something like this (probably a little half-assed, and definitely very
> untested :-).

Nevertheless, it seems to work well enough :-) The only bug I've
noticed is that calculations related to bi_rw need to be unsigned
long, for 64 bit compatibility, i.e.

+#define bio_set_prio(bio, prio)	do {			\
+	WARN_ON(prio >= (1 << BIO_PRIO_BITS));		\
+	(bio)->bi_rw &= ((1UL << BIO_PRIO_SHIFT) - 1);	\
+	(bio)->bi_rw |= ((unsigned long) (prio) << BIO_PRIO_SHIFT);	\
+} while (0)

I've adapted your per-process IO priority idea, and used it as
follows:

--- linux-2.6.7-orig/include/linux/sched.h	Wed Jun 16 02:18:57 2004
+++ linux-2.6.7/include/linux/sched.h	Sun Jul 11 15:00:31 2004
@@ -505,6 +505,7 @@ struct task_struct {
 	struct backing_dev_info *backing_dev_info;
 
 	struct io_context *io_context;
+	int ioprio;
 
 	unsigned long ptrace_message;
 	siginfo_t *last_siginfo; /* For ptrace use.  */
--- linux-2.6.7-orig/fs/buffer.c	Wed Jun 16 02:19:36 2004
+++ linux-2.6.7/fs/buffer.c	Mon Jul 12 08:25:41 2004
@@ -2789,6 +2789,8 @@ void submit_bh(int rw, struct buffer_hea
 	bio->bi_end_io = end_bio_bh_io_sync;
 	bio->bi_private = bh;
 
+	bio_set_prio(bio, current->ioprio);
+
 	submit_bio(rw, bio);
 }
 
--- linux-2.6.7-orig/drivers/block/ll_rw_blk.c	Sun Jul 11 14:20:07 2004
+++ linux-2.6.7/drivers/block/ll_rw_blk.c	Mon Jul 12 08:20:41 2004
@@ -2320,7 +2320,7 @@ static inline void blk_partition_remap(s
 	if (bdev != bdev->bd_contains) {
 		struct hd_struct *p = bdev->bd_part;
 
-		switch (bio->bi_rw) {
+		switch (bio->bi_rw & BIO_RW) {
 		case READ:
 			p->read_sectors += bio_sectors(bio);
 			p->reads++;
@@ -2451,7 +2451,7 @@ void submit_bio(int rw, struct bio *bio)
 
 	BIO_BUG_ON(!bio->bi_size);
 	BIO_BUG_ON(!bio->bi_io_vec);
-	bio->bi_rw = rw;
+	bio->bi_rw |= rw;
 	if (rw & WRITE)
 		mod_page_state(pgpgout, count);
 	else

Because I'm lazy, I'm using a default priority of zero, so I
don't need any explicit initialization.

I've been playing with this for a few hours, and even a
request-happy load with random accesses through AIO, which
normally basically kills the machine, doesn't impress my
high-priority reader anymore. I haven't looked into fairness
issues, though.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  parent reply	other threads:[~2004-07-12 23:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22  4:25 elevator priorities vs. full request queues Werner Almesberger
2004-06-22  7:48 ` Jens Axboe
2004-06-22  8:26   ` Werner Almesberger
2004-06-22 10:14     ` Jens Axboe
2004-06-22 19:08       ` Werner Almesberger
2004-06-23 10:14         ` Jens Axboe
2004-06-23 12:46           ` Werner Almesberger
2004-06-23 16:46             ` Jens Axboe
2004-06-23 16:57               ` Werner Almesberger
2004-06-23 17:00                 ` Jens Axboe
2004-06-23 23:02                   ` Werner Almesberger
2004-07-12 23:52           ` Werner Almesberger [this message]
2004-07-13  5:37             ` Jens Axboe
2004-07-13 12:29               ` Werner Almesberger
2004-07-13 12:35                 ` Jens Axboe
2004-07-13 16:36                   ` Werner Almesberger
2004-07-13 16:59                     ` Jens Axboe

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=20040712205227.A12285@almesberger.net \
    --to=wa@almesberger.net \
    --cc=axboe@suse.de \
    --cc=linux-fsdevel@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 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.