From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: scsi-mq + open-iscsi support patches..?
Date: Fri, 01 Nov 2013 09:46:23 -0500 [thread overview]
Message-ID: <5273BEBF.2090008@cs.wisc.edu> (raw)
In-Reply-To: <1382997816.19256.767.camel@haakon3.risingtidesystems.com>
On 10/28/13 5:03 PM, Nicholas A. Bellinger wrote:
> Hi Mike,
>
> Just curious as to the status of the scsi-mq conversion patches for
> open-iscsi that you where working on a while back..?
>
> I'm asking because recently I've been spending alot of time with scsi-mq
> + virtio-scsi, and would really to start banging on iser-target ports
> using an scsi-mq enabled iser-initiator as well..
>
> So that said, are there any blockers holding things up towards getting a
> working prototype..?
>
Just time. Just finished a release at work and just got back from
vacation so hoping to work on this some more in the next weeks.
On a related note, some iscsi vendor has been hitting a crash with your
tree. Have you rebased it it to take in Christoph's changes and fixes
that are in Jens's tree? The code here
https://git.kernel.org/cgit/linux/kernel/git/nab/target-pending.git/log/?h=scsi-mq
looks ok. That is the current code right?
next prev parent reply other threads:[~2013-11-01 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 22:03 scsi-mq + open-iscsi support patches..? Nicholas A. Bellinger
2013-11-01 14:46 ` Mike Christie [this message]
2013-11-01 20:37 ` Nicholas A. Bellinger
2013-11-02 16:10 ` Jayamohan Kallickal
2013-11-04 18:56 ` Nicholas A. Bellinger
2013-11-27 2:46 ` kedacomkernel
2013-11-27 18:43 ` Nicholas A. Bellinger
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=5273BEBF.2090008@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=open-iscsi@googlegroups.com \
--cc=target-devel@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