scsi-mq + open-iscsi support patches..?

scsi-mq + open-iscsi support patches..?

[Nicholas A. Bellinger]

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..?

--nab

Re: scsi-mq + open-iscsi support patches..?

[Mike Christie]

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?

Re: scsi-mq + open-iscsi support patches..?

[Mike Christie]

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?

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.

Re: scsi-mq + open-iscsi support patches..?

[Nicholas A. Bellinger]

On Fri, 2013-11-01 at 09:46 -0500, Mike Christie wrote:
> 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.
> 

<nod>

Btw, I'm happy to help move things along here too, and have a few extra
cycles to spare..

> On a related note, some iscsi vendor has been hitting a crash with your 
> tree.

I got an email from Jayamohan recently, but the OOPs did not appear to
be scsi-mq related..

>  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?
> 

It's current as of a few weeks ago, but does not include the very latest
blk-mq code that's now in next from Jens.

I'll be rebasing once blk-mq hits mainline over the next weeks..  ;)

--nab

Re: scsi-mq + open-iscsi support patches..?

[Nicholas A. Bellinger]

On Fri, 2013-11-01 at 09:46 -0500, Mike Christie wrote:
> 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.
> 

<nod>

Btw, I'm happy to help move things along here too, and have a few extra
cycles to spare..

> On a related note, some iscsi vendor has been hitting a crash with your 
> tree.

I got an email from Jayamohan recently, but the OOPs did not appear to
be scsi-mq related..

>  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?
> 

It's current as of a few weeks ago, but does not include the very latest
blk-mq code that's now in next from Jens.

I'll be rebasing once blk-mq hits mainline over the next weeks..  ;)

--nab

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.

Re: some iscsi vendor has been hitting a crash

[Thomas Glanzmann]

Hello Mike,

* Mike Christie <michaelc@cs.wisc.edu> [2013-11-01 15:56]:
> On a related note, some iscsi vendor has been hitting a crash with
> your tree.

I hit an 'IO stall' with the tree, but was not able to reproduce this.
Has this vendor information on it (dmesg, OOPS)? I reverted back to
RTSOS for production classes that I do not give myself, but will run the
Nab's tree as soon as I give a VMware class myself in order to reproduce
the issue and than track it down.

Cheers,
        Thomas

Re: some iscsi vendor has been hitting a crash

[Nicholas A. Bellinger]

On Fri, 2013-11-01 at 22:28 +0100, Thomas Glanzmann wrote:
> Hello Mike,
> 
> * Mike Christie <michaelc@cs.wisc.edu> [2013-11-01 15:56]:
> > On a related note, some iscsi vendor has been hitting a crash with
> > your tree.
> 
> I hit an 'IO stall' with the tree, but was not able to reproduce this.
> Has this vendor information on it (dmesg, OOPS)? I reverted back to
> RTSOS for production classes that I do not give myself, but will run the
> Nab's tree as soon as I give a VMware class myself in order to reproduce
> the issue and than track it down.
> 

Hey Thomas,

Mike's talking about the WIP scsi-mq -> blk-mq initiator stack here, and
not specifically about anything related to target code.

--nab

Re: some iscsi vendor has been hitting a crash

[Thomas Glanzmann]

Hallo Nab,

> Mike's talking about the WIP scsi-mq -> blk-mq initiator stack here,
> and not specifically about anything related to target code.

I see. Thanks. I'll keep you posted.

Cheers,
        Thomas

RE: scsi-mq + open-iscsi support patches..?

[Jayamohan Kallickal]

[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]


-----Original Message-----
From: open-iscsi@googlegroups.com [mailto:open-iscsi@googlegroups.com] On Behalf Of Nicholas A. Bellinger
Sent: Friday, November 01, 2013 1:37 PM
To: Mike Christie
Cc: open-iscsi@googlegroups.com; linux-scsi; LKML; target-devel; Or Gerlitz
Subject: Re: scsi-mq + open-iscsi support patches..?

On Fri, 2013-11-01 at 09:46 -0500, Mike Christie wrote:
> 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.
> 

<nod>

>Btw, I'm happy to help move things along here too, and have a few extra cycles to spare..

>> On a related note, some iscsi vendor has been hitting a crash with 
>> your tree.

>I got an email from Jayamohan recently, but the OOPs did not appear to be scsi-mq related..

I do see the crash on my Ubuntu VM running on VirtualBox  but don't see the crash on a Standalone system. 
Attaching the screenshot

>  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/lo
> g/?h=scsi-mq
> 
> looks ok. That is the current code right?
> 

It's current as of a few weeks ago, but does not include the very latest blk-mq code that's now in next from Jens.

I'll be rebasing once blk-mq hits mainline over the next weeks..  ;)

--nab

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/groups/opt_out.

[-- Attachment #2: Ubuntu-VM-crash.png --]
[-- Type: image/png, Size: 27707 bytes --]

Re: scsi-mq + open-iscsi support patches..?

[Nicholas A. Bellinger]

On Sat, 2013-11-02 at 16:10 +0000, Jayamohan Kallickal wrote:

<SNIP>

> >> On a related note, some iscsi vendor has been hitting a crash with 
> >> your tree.
> 
> >I got an email from Jayamohan recently, but the OOPs did not appear to be scsi-mq related..
> 
> I do see the crash on my Ubuntu VM running on VirtualBox  but don't see the crash on a Standalone system. 
> Attaching the screenshot
> 

Hi Jayamohan,

Care to enable the virtual serial port for this VM in order to grab the
full dmesg output..?

Also, an idea of what SATA emulation is being used here would be helpful
as well.  (eg: lspci -vvv for the ATA device on the running system)

--nab

Re: Re: scsi-mq + open-iscsi support patches..?

[kedacomkernel]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1246 bytes --]

Hi all，
	I used target-pending/scsi-mq to test intel ahci，but it can't work.I modify some places, now it can work.But still met hung task or oops.
Who can receive my patch for that?

Thanks!
Jianpeng Ma
>On Sat, 2013-11-02 at 16:10 +0000, Jayamohan Kallickal wrote:
>
><SNIP>
>
>> >> On a related note, some iscsi vendor has been hitting a crash with 
>> >> your tree.
>> 
>> >I got an email from Jayamohan recently, but the OOPs did not appear to be scsi-mq related..
>> 
>> I do see the crash on my Ubuntu VM running on VirtualBox  but don't see the crash on a Standalone system. 
>> Attaching the screenshot
>> 
>
>Hi Jayamohan,
>
>Care to enable the virtual serial port for this VM in order to grab the
>full dmesg output..?
>
>Also, an idea of what SATA emulation is being used here would be helpful
>as well.  (eg: lspci -vvv for the ATA device on the running system)
>
>--nab
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.htmlÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

Re: Re: scsi-mq + open-iscsi support patches..?

[kedacomkernel]

Hi all，
	I used target-pending/scsi-mq to test intel ahci，but it can't work.I modify some places, now it can work.But still met hung task or oops.
Who can receive my patch for that?

Thanks!
Jianpeng Ma
>On Sat, 2013-11-02 at 16:10 +0000, Jayamohan Kallickal wrote:
>
><SNIP>
>
>> >> On a related note, some iscsi vendor has been hitting a crash with 
>> >> your tree.
>> 
>> >I got an email from Jayamohan recently, but the OOPs did not appear to be scsi-mq related..
>> 
>> I do see the crash on my Ubuntu VM running on VirtualBox  but don't see the crash on a Standalone system. 
>> Attaching the screenshot
>> 
>
>Hi Jayamohan,
>
>Care to enable the virtual serial port for this VM in order to grab the
>full dmesg output..?
>
>Also, an idea of what SATA emulation is being used here would be helpful
>as well.  (eg: lspci -vvv for the ATA device on the running system)
>
>--nab
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Re: scsi-mq + open-iscsi support patches..?

[Nicholas A. Bellinger]

Hi Jianpeng,

(Trimming CC's)

On Wed, 2013-11-27 at 10:46 +0800, kedacomkernel wrote:
> Hi all，
> 	I used target-pending/scsi-mq to test intel ahci，but it can't work.I
> modify some places, now it can work.But still met hung task or oops.

So after looking at your patches sent offlist, I don't exactly
understand why they are necessary for AHCI to function.

> Who can receive my patch for that?

Please repost your patches to linux-scsi, with the specifics of each bug
you've encountered, and why each patch is necessary to address the
issue.

Thanks!

--nab