mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What's in linux-2.6-block.git
Date: Wed, 13 Sep 2006 13:59:04 +0300	[thread overview]
Message-ID: <200609131359.04972.a1426z@gawab.com> (raw)

Jens Axboe  wrote:
> This lists the main features of the 'block' branch, which is bound for
> Linus when 2.6.19 opens:
>
> - Splitting of request->flags into two parts:
>         - cmd type
>         - modified flags
>   Right now it's a bit of a mess, splitting this up invites a cleaner
>   usage and also enables us to implement generic "messages" passed on
>   the regular queue for the device.
>
> - Abstract out the request back merging and put it into the core io
>   scheduler layer. Cleans up all the io schedulers, and noop gets
>   merging for "free".
>
> - Abstract out the rbtree sorting. Gets rid of duplicated code in
>   as/cfq/deadline.
>
> - General shrinkage of the request structure.
>
> - Killing dynamic rq private structures in deadline/as/cfq. This should
>   speed up the io path somewhat, as we avoid allocating several
>   structures (struct request + scheduler private request) for each io
>   request.
>
> - meta data io logging for blktrace.
>
> - CFQ improvements.
>
> - Make the block layer configurable through Kconfig (David Howells).
>
> - Lots of cleanups.

Does it also address the strange "max_sectors_kb<>192 causes a 50%-slowdown" 
problem?


Thanks!

--
Al


             reply	other threads:[~2006-09-13 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 10:59 Al Boldi [this message]
2006-09-13 10:59 ` Jens Axboe
2006-09-13 11:35   ` Al Boldi
2006-09-13 11:56     ` Jens Axboe
2006-09-13 17:52       ` Al Boldi
2006-09-13 14:23     ` John Stoffel
2006-09-13 17:52       ` Al Boldi
2006-09-14 19:46         ` John Stoffel
  -- strict thread matches above, loose matches on Subject: below --
2006-09-12 10:11 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=200609131359.04972.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --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

all inboxes | Powered by JetHome®