linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Ming Lei <ming.lei@redhat.com>,
	"chenxiang (M)" <chenxiang66@hisilicon.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Linuxarm <linuxarm@huawei.com>,
	Steffen Maier <maier@linux.ibm.com>
Subject: Re: DIF/DIX issue related to config CONFIG_SCSI_MQ_DEFAULT
Date: Fri, 30 Nov 2018 11:26:07 +0000	[thread overview]
Message-ID: <e0e07583-98ca-4fc5-e60d-055e5474c084@huawei.com> (raw)
In-Reply-To: <20181130011935.GA7573@ming.t460p>

+

On 30/11/2018 01:19, Ming Lei wrote:
> On Wed, Nov 28, 2018 at 10:50:11AM +0800, chenxiang (M) wrote:
>> Hi  Lei Ming,
>>
>> 在 2018/11/27 21:08, Ming Lei 写道:
>>> On Tue, Nov 27, 2018 at 05:55:45PM +0800, chenxiang (M) wrote:
>>>> Hi all,
>>>>
>>>> There is a issue which may be related to CONFIG_SCSI_MQ_DEFAULT: before we
>>>> developed DIF/DIX feature on kernel 4.18 (disable CONFIG_SCSI_MQ_DEFAULT
>>>> default), and
>>>> it works well.
>>> I guess you are testing hisi_sas_v3_hw, does 4.18 work with
>>> 'scsi_mod.use_blk_mq=Y'? If yes, you may run 'git bisect' to figure out
>>> which commit is the 1st bad one.
>>
>> Yes, i am testing hisi_sas_v3_hw, if 4.18 with 'scsi_mod.use_blk_mq=Y' ,
>> there is still a issue, and
>> the log is as attached ;
>>
>>>
>>>> But when we switch to kernel 4.19-rc1 and 4.20-rc1, Call
>>>> trace as follow occurs when running fio and if disable config
>>>> CONFIG_SCSI_MQ_DEFAULT,
>>>> then it works well. Also if switch ioengine=libaio to ioengine=psync, it
>>>> seems also work well. Do you have any idea or encounter similar issue?
>>> I tested scsi-debug via 'dix=1 dif=1', looks everything is fine, are you
>>> using direct io or not?
>> Yes, i use direct io.
>> I also test scsi-debug on kernel 4.19, and there seems be some other issue,
>> and i am not sure
>> whethere there is something wrong my operation:
>>
>> root@(none)$ insmod scsi_debug.ko dif=1 dix=1 virtual_gb=120
>
> Hi chenxiang,
>
> For DIX/DIF test, I think you need to pass 'dev_size_mb=XXX' instead of
> 'virtual_gb'.
>
> I just run FIO over 'scsi_debug dev_size_mb=896 max_luns=1 dif=1 dix=1'
> on one apm-mustang-ev3 board, and looks everything is fine. You may run
> the same test on your D06 and see if it is fine.
>
> Please check if you may reproduce the list corruption issue on v4.18 with
> hisi_sas_v3_hw.
>

Hi Ming,

Thanks for your support.

We have also noticed that if we just enable DIF in hisi_sas (with MQ), 
and not DIX, then no issue.

I did also noticed mail "[PATCH v2 01/23] zfcp: make DIX experimental, 
disabled, and independent of DIF", where DIX is made experimental.

For now we may not support DIX. It seems to have issues. We wanted to 
try 3008 card on our system, but it does not seem to support DIX 0-3.

BTW, chen xiang said your commnand works ok on our HW. He can confirm.

Thanks again,
John

> Thanks,
> Ming
>
> .
>



  reply	other threads:[~2018-11-30 11:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  9:55 DIF/DIX issue related to config CONFIG_SCSI_MQ_DEFAULT chenxiang (M)
2018-11-27 13:08 ` Ming Lei
2018-11-28  3:37   ` chenxiang (M)
2018-11-29 18:17     ` Ming Lei
     [not found]   ` <6c573f36-60d8-0631-e9ac-dacd72f6c8ad@hisilicon.com>
2018-11-29  0:54     ` Ming Lei
2018-11-30  1:19     ` Ming Lei
2018-11-30 11:26       ` John Garry [this message]
2018-12-04  3:55         ` Martin K. Petersen
     [not found]           ` <45193ec6-6398-3953-4833-88ca2057971a@huawei.com>
2018-12-05  2:22             ` Martin K. Petersen
2018-12-05 15:27               ` John Garry
2018-12-06  4:22                 ` Martin K. Petersen
2018-12-06 17:33                   ` John Garry
2018-12-07  3:20                     ` Martin K. Petersen
2018-12-05  2:56       ` Martin K. Petersen
2018-11-27 20:22 ` Ewan D. Milne
2018-11-28  3:11   ` chenxiang (M)

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=e0e07583-98ca-4fc5-e60d-055e5474c084@huawei.com \
    --to=john.garry@huawei.com \
    --cc=chenxiang66@hisilicon.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=maier@linux.ibm.com \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    /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).