From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Linux 2.6.20-rc1
Date: Thu, 14 Dec 2006 19:03:18 -0600 [thread overview]
Message-ID: <4581F456.5040708@shaw.ca> (raw)
In-Reply-To: <fa.p3mZcZJUV5vbz5aYUBbt4rJjr2A@ifi.uio.no>
Alistair John Strachan wrote:
> I bisected all the way down to 0e75f9063f5c55fb0b0b546a7c356f8ec186825e, which
> git reckons is the culprit. I wasn't able to revert this commit to test,
> because it has conflicts.
>
> Any ideas?
That would be this one I assume?
[PATCH] block: support larger block pc requests
author Mike Christie <michaelc@cs.wisc.edu>
Fri, 1 Dec 2006 09:40:55 +0000 (10:40 +0100)
committer Jens Axboe <jens.axboe@oracle.com>
Fri, 1 Dec 2006 09:40:55 +0000 (10:40 +0100)
commit 0e75f9063f5c55fb0b0b546a7c356f8ec186825e
tree db138f641175403546c2147def4b405f3ff453a8
parent ad2d7225709b11da47e092634cbdf0591829ae9c
[PATCH] block: support larger block pc requests
This patch modifies blk_rq_map/unmap_user() and the cdrom and scsi_ioctl.c
users so that it supports requests larger than bio by chaining them
together.
Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-12-15 1:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.RIN4HRPnLGt7UFAh8INm8D0Re5k@ifi.uio.no>
[not found] ` <fa.bn+19zl5p6JLw04wsJAH4QbLSps@ifi.uio.no>
[not found] ` <fa.hRBfOTtQdNUe6Lr4YfYDijpzP5g@ifi.uio.no>
[not found] ` <fa.p3mZcZJUV5vbz5aYUBbt4rJjr2A@ifi.uio.no>
2006-12-15 1:03 ` Robert Hancock [this message]
2006-12-14 2:06 Linux 2.6.20-rc1 Linus Torvalds
2006-12-14 2:46 ` Gene Heskett
2006-12-14 3:32 ` Linus Torvalds
2006-12-14 5:36 ` Gene Heskett
2006-12-14 13:59 ` Alessandro Suardi
2006-12-14 14:18 ` Steve WIse
2006-12-14 15:48 ` Alan
2006-12-14 19:30 ` Alistair John Strachan
2006-12-14 19:57 ` Linus Torvalds
2006-12-14 20:05 ` Jeff Garzik
2006-12-14 20:16 ` Alistair John Strachan
2006-12-14 20:28 ` Jens Axboe
2006-12-14 20:33 ` Jeff Garzik
2006-12-14 20:36 ` Jens Axboe
2006-12-14 20:48 ` Jens Axboe
2006-12-14 21:13 ` Alistair John Strachan
2006-12-14 21:20 ` Jens Axboe
2006-12-15 0:48 ` Alistair John Strachan
2006-12-15 1:41 ` Alistair John Strachan
2006-12-16 21:36 ` Linus Torvalds
2006-12-16 22:28 ` Alistair John Strachan
2006-12-16 22:31 ` Jeff Garzik
2006-12-16 23:00 ` Alistair John Strachan
2006-12-18 18:32 ` Jens Axboe
2006-12-18 18:41 ` Jens Axboe
2006-12-14 21:33 ` Jeff Garzik
2006-12-14 21:44 ` Alistair John Strachan
2006-12-14 21:50 ` Jeff Garzik
2006-12-14 22:33 ` Alistair John Strachan
2006-12-19 12:41 ` Jens Axboe
2006-12-19 14:32 ` Robert Hancock
2006-12-19 14:38 ` Jens Axboe
2006-12-19 14:50 ` Jens Axboe
2006-12-19 17:49 ` Linus Torvalds
2006-12-14 21:53 ` Jeff Garzik
2006-12-14 20:32 ` Nicolas Mailhot
2006-12-14 23:22 ` Jeff Garzik
2006-12-14 23:33 ` Nicolas Mailhot
2006-12-15 16:50 ` Bill Davidsen
2006-12-15 17:28 ` Alan
2006-12-18 21:57 ` Bill Davidsen
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=4581F456.5040708@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).