From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What's in linux-2.6-block.git for 2.6.27
Date: Thu, 26 Jun 2008 19:37:55 +0200 [thread overview]
Message-ID: <20080626173754.GC20851@kernel.dk> (raw)
In-Reply-To: <20080626233440K.fujita.tomonori@lab.ntt.co.jp>
On Thu, Jun 26 2008, FUJITA Tomonori wrote:
> On Thu, 26 Jun 2008 13:54:04 +0200
> Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > Hi,
> >
> > So this time it's a little beyond just block stuff, since the
> > generic-ipi branch is included (in preparation for block parts actually
> > using that code).
> >
> > - xen block bits
> >
> > - Write starvation fix for 'AS', a very long standing bug
> >
> > - CFQ using the message trace for debugging.
> >
> > - Ability to inject messages into the blktrace stream from user space,
> > which helps annotate a longer running trace where you make changes
> > meanwhile.
> >
> > - Finally kill off request_queue_t typedef.
> >
> > - The data integrity block parts.
> >
> > - Export of the disk read-only attribute in sysfs
> >
> > - The generic-ipi smp helpers and a slew of arch conversions.
> >
> > All of the above can be viewed/tested in the for-next branch, which is
> > what Stephen is pulling as well. For manual code browsing, go to gitweb
> > here:
>
> Can you add a patch to add bounce support to blk_rq_map_user_iov?
>
> http://marc.info/?l=linux-scsi&m=121299573730764&w=2
Yep, done.
--
Jens Axboe
next prev parent reply other threads:[~2008-06-26 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 11:54 What's in linux-2.6-block.git for 2.6.27 Jens Axboe
2008-06-26 12:22 ` Oliver Pinter
2008-06-26 12:26 ` Jens Axboe
2008-06-26 12:33 ` Oliver Pinter
2008-06-26 14:36 ` FUJITA Tomonori
2008-06-26 17:37 ` Jens Axboe [this message]
2008-06-27 9:00 ` Milan Broz
2008-06-27 9:04 ` 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=20080626173754.GC20851@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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