From: Andrew Morton <akpm@linux-foundation.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What's in linux-2.6-block.git for 2.6.24
Date: Fri, 21 Sep 2007 02:15:05 -0700 [thread overview]
Message-ID: <20070921021505.99c37589.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070921085711.GG2367@kernel.dk>
On Fri, 21 Sep 2007 10:57:11 +0200 Jens Axboe <jens.axboe@oracle.com> wrote:
> Hi,
>
> This details the contents of the block git repo of items that are bound
> for a 2.6.24 merge. The SCSI data buffer accessor patch from Tomo will
> also be going in through the block tree, but it's not merged up yet.
> That's mainly due to my laziness, not because the code isn't ready. That
> will happen sometime during today.
>
> Misc bits:
> - Various bug fixes from Neil Brown, part of his larger patchset for
> allowing arbitrarily sized bios.
> - Various little bug fixes and documentation updates.
>
> Barriers:
> - The empty bio barrier patches from me. These allow sending down a bio
> with no data attached, for insertion a barrier in a request queue.
> They are useful for dm and md, but also cleans up the sync
> blkdev_issue_flush() interface - it's now no longer an addon hack, but
> just a natural use of empty bio barriers.
That sounds useful.
> SG chaining bits:
> - This is the bulk of the patchset. It consists of three major
> components:
>
> - sglist-core, which add helpers for iterating sg lists and
> switches the block layer and SCSI to use those. Should not
> have any functional changes.
> - sglist-drivers, which converts drivers to use the sg list
> helpers. Again, should not contain functional changes.
> - sglist-arch, which adds support to most architectures and
> actually enables sg chaining.
>
> The goal of sg chaining is to allow support for very large sgtables,
> without requiring that they be allocated from one contigious piece of
> memory.
Presumably sg chaining means more overhead on the IO submission paths? If
so, has this been quantified?
next prev parent reply other threads:[~2007-09-21 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 8:57 What's in linux-2.6-block.git for 2.6.24 Jens Axboe
2007-09-21 9:15 ` Andrew Morton [this message]
2007-09-21 9:24 ` Jens Axboe
2007-09-21 9:36 ` Jens Axboe
2007-09-23 13:19 ` Torsten Kaiser
2007-09-23 13:55 ` FUJITA Tomonori
2007-09-23 13:55 ` FUJITA Tomonori
2007-09-23 15:31 ` Torsten Kaiser
2007-09-24 18:48 ` Torsten Kaiser
2007-09-25 5:52 ` Torsten Kaiser
2007-09-23 14:11 ` Alan Cox
2007-09-23 15:40 ` Torsten Kaiser
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=20070921021505.99c37589.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.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 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.