All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCHSET] 0/15 IO scheduler improvements
Date: Thu, 13 Jul 2006 14:46:23 +0200	[thread overview]
Message-ID: <11527947982769-git-send-email-axboe@suse.de> (raw)

Hi,

This is a continuation of the patches posted yesterday, I continued
to build on them. The patch series does:

- Move the hash backmerging into the elevator core.
- Move the rbtree handling into the elevator core.
- Abstract the FIFO handling into the elevator core.
- Kill the io scheduler private requests, that require allocation/free
  for each request passed through the system.

The result is a faster elevator core (and faster IO schedulers), with a
nice net reduction of kernel text and code as well.

If you have time, please give this patch series a test spin just to
verify that everything still works for you. Thanks!

 block/as-iosched.c       |  650 ++++++++++-------------------------------------
 block/cfq-iosched.c      |  498 +++++++++---------------------------
 block/deadline-iosched.c |  462 +++++----------------------------
 block/elevator.c         |  266 +++++++++++++++++--
 block/ll_rw_blk.c        |    9 
 include/linux/blkdev.h   |   29 +-
 include/linux/elevator.h |   32 ++
 include/linux/rbtree.h   |    2 
 lib/rbtree.c             |    6 
 9 files changed, 649 insertions(+), 1305 deletions(-)


--
Jens Axboe


             reply	other threads:[~2006-07-13 12:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 12:46 Jens Axboe [this message]
2006-07-13 12:46 ` [PATCH] 1/15 elevator: move the backmerging logic into the elevator core Jens Axboe
2006-07-13 12:46 ` [PATCH] 2/15 rbtree: fixed reversed RB_EMPTY_NODE and rb_next/prev Jens Axboe
2006-07-13 12:46 ` [PATCH] 3/15 elevator: abstract out the rbtree sort handling Jens Axboe
2006-07-13 12:46 ` [PATCH] 4/15 as-iosched: migrate to using the elevator rb functions Jens Axboe
2006-07-13 12:46 ` [PATCH] 5/15 cfq-iosched: " Jens Axboe
2006-07-13 12:46 ` [PATCH] 6/15 deadline-iosched: " Jens Axboe
2006-07-13 12:46 ` [PATCH] 7/15 elevator: introduce a way to reuse rq for internal FIFO handling Jens Axboe
2006-07-13 12:46 ` [PATCH] 8/15 cfq-iosched: convert to using the FIFO elevator defines Jens Axboe
2006-07-13 12:46 ` [PATCH] 9/15 as-iosched: reuse rq for fifo Jens Axboe
2006-07-13 12:46 ` [PATCH] 10/15 as-iosched: remove arq->is_sync member Jens Axboe
2006-07-13 12:46 ` [PATCH] 11/15 deadline-iosched: remove elevator private drq request type Jens Axboe
2006-07-13 12:46 ` [PATCH] 12/15 cfq-iosched: remove the crq flag functions/variable Jens Axboe
2006-07-13 12:46 ` [PATCH] 13/15 Add one more pointer to struct request for IO scheduler usage Jens Axboe
2006-07-13 12:46 ` [PATCH] 14/15 cfq-iosched: kill crq Jens Axboe
2006-07-13 12:46 ` [PATCH] 15/15 as-iosched: kill arq Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:50 [PATCHSET] 0/15 IO scheduler improvements Al Boldi
2006-07-14  7:15 ` Jens Axboe
2006-07-14 19:53   ` Al Boldi
2006-07-15 11:06     ` Jens Axboe
2006-07-15 12:35       ` Al Boldi
2006-07-15 17:46         ` Jens Axboe
2006-07-15 20:27           ` Al Boldi
2006-07-16 11:26             ` 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=11527947982769-git-send-email-axboe@suse.de \
    --to=axboe@suse.de \
    --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 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.