From: Jens Axboe <jens.axboe@oracle.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
James.Bottomley@SteelEye.com, hch@infradead.org,
dougg@torque.net, James.Smart@Emulex.Com,
linux-scsi@vger.kernel.org
Subject: Re: SMP pass through interface via bsg
Date: Mon, 2 Apr 2007 20:30:02 +0200 [thread overview]
Message-ID: <20070402183002.GF15273@kernel.dk> (raw)
In-Reply-To: <46114C24.1030003@cs.wisc.edu>
On Mon, Apr 02 2007, Mike Christie wrote:
> Jens Axboe wrote:
> > On Tue, Apr 03 2007, FUJITA Tomonori wrote:
> >> From: James Bottomley <James.Bottomley@SteelEye.com>
> >> Subject: Re: SMP pass through interface via bsg
> >> Date: Mon, 02 Apr 2007 12:01:41 -0500
> >>
> >>> On Tue, 2007-04-03 at 01:43 +0900, FUJITA Tomonori wrote:
> >>>> OK. I found another bug in smp_test tool (sends bogus response buffer
> >>>> len to kernel). I've uploaded a new patch:
> >>>>
> >>>> http://zaal.org/bsg/smp-test2.diff
> >>> That sort of works; you have a final bug in that the manufacturer info
> >>> response frame is 64 bytes, not 128 bytes, but with that corrected
> >>> everything goes through and I get the result back:
> >>>
> >>> hobholes:~# /home/jejb/git/sgv4-tools/smp_test /sys/class/bsg/expander-2\:0
> >>> SAS-1.1 format: 0
> >>> vendor identification: LSILOGIC
> >>> product identification: SASx12 A.0
> >>> product revision level:
> >>>
> >>> So we can class this one as a success ...
> >>>
> >>> Thanks!
> >> Great! Thanks. I'll try to finish the mpt driver's hook
> >> sometime. Finally, We have a bsg user (though it also needs proper
> >> bidi support).
> >>
> >> Jens, what remains to be done before bsg is merged into mainline?
> >
> > Well the bi-dir stuff and sg v4 design were the two bits that needed to
> > get done before pushing bsg made sense, so we are getting there...
> > Probably a 2.6.23 target, leaving the bidi bits a revision cycle to get
> > sorted out.
> >
>
> Could we get the bidi parts in without having to do the other sg clean
> ups (my patches to merge the blk_rq_map* with the scsi ULD (sg, etc,
> etc) equivalents or do the clean ups have to be done first?
IMO the sg cleanups are an orthogonal effort.
--
Jens Axboe
next prev parent reply other threads:[~2007-04-02 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 2:49 SMP pass through interface via bsg FUJITA Tomonori
2007-04-02 3:57 ` James Bottomley
2007-04-02 12:43 ` FUJITA Tomonori
2007-04-02 16:02 ` James Bottomley
2007-04-02 16:27 ` FUJITA Tomonori
2007-04-02 16:43 ` FUJITA Tomonori
2007-04-02 17:01 ` James Bottomley
2007-04-02 17:54 ` FUJITA Tomonori
2007-04-02 18:12 ` Jens Axboe
2007-04-02 18:32 ` Mike Christie
2007-04-02 18:30 ` Jens Axboe [this message]
2007-04-15 17:14 ` Boaz Harrosh
2007-04-02 18:55 ` FUJITA Tomonori
2007-04-02 13:45 ` James Smart
2007-04-02 15:47 ` Douglas Gilbert
2007-04-02 17:10 ` James Bottomley
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=20070402183002.GF15273@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=James.Bottomley@SteelEye.com \
--cc=James.Smart@Emulex.Com \
--cc=dougg@torque.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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.