From: Mike Christie <michaelc@cs.wisc.edu>
To: boutcher@cs.umn.edu
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.14
Date: Wed, 09 Nov 2005 12:30:54 -0600 [thread overview]
Message-ID: <4372405E.6020302@cs.wisc.edu> (raw)
In-Reply-To: <20051109150709.GA19002@cs.umn.edu>
Dave C Boutcher wrote:
> On Wed, Nov 09, 2005 at 05:09:11AM +0000, Christoph Hellwig wrote:
>
>>On Tue, Nov 08, 2005 at 05:35:46PM -0600, Dave C Boutcher wrote:
>>
>>>On Sat, Nov 05, 2005 at 10:18:11AM -0600, James Bottomley wrote:
>>>
>>>>This is Part I of the pending SCSI patches (I still need to go over all
>>>>the flood that came in after 2.6.14 was declared).
>>>>
>>>>This patch is available from:
>>>>
>>>>master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-for-linus-2.6.git
>>>
>>>James, I note that my favorite masterpiece of ibmvscsis.c is not
>>>currently included. Does that fall into part of the "flood"?
>>
>>it shouldn't go in. we already have a version using the proper target
>>framework, that should be imroved upon to get production quality and then
>>merged.
>
>
> My only problem with that is the amount of time it is going to keep the
> driver out of the tree. I'm happy to commit to merging to a converged
> infrastructure as soon as it is available.
>
Your driver needs some work as it is. We are trying to kill scsi_request
usage, your bio segments are wrong if cluster is not used (iscsi in
mainline does not use clustering), and you could use bio_map_kern().
There are others, but I did not review it so closely.
next prev parent reply other threads:[~2005-11-09 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 16:18 [GIT PATCH] SCSI updates for 2.6.14 James Bottomley
2005-11-05 17:44 ` Linus Torvalds
2005-11-05 18:13 ` James Bottomley
2005-11-05 18:25 ` Jeff Garzik
2005-11-05 18:33 ` James Bottomley
2005-11-05 18:37 ` Jeff Garzik
[not found] ` <Pine.LNX.4.64.0511051031250.3316@g5.osdl.org>
[not found] ` <1131216913.3614.15.camel@mulgrave>
2005-11-05 19:32 ` Linus Torvalds
2005-11-08 23:35 ` Dave C Boutcher
2005-11-09 5:09 ` Christoph Hellwig
2005-11-09 15:07 ` Dave C Boutcher
2005-11-09 18:30 ` Mike Christie [this message]
2005-11-09 18:35 ` Mike Christie
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=4372405E.6020302@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=boutcher@cs.umn.edu \
--cc=hch@infradead.org \
--cc=linux-scsi@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.