linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bernard Metzler <BMT@zurich.ibm.com>, Yi Zhang <yi.zhang@redhat.com>
Cc: Robert Pearson <rpearsonhpe@gmail.com>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: Issus with blktest/srp on 5.15-rc1 and rdma_rxe
Date: Fri, 17 Sep 2021 19:56:20 -0700	[thread overview]
Message-ID: <79755291-a36f-535c-03b8-73178f80ca5e@acm.org> (raw)
In-Reply-To: <OFC7347FF0.D24DF679-ON00258753.002DFE5F-00258753.002E19D7@ibm.com>

On 9/17/21 01:23, Bernard Metzler wrote:
> -----"Yi Zhang" <yi.zhang@redhat.com> wrote: -----
>> Just try use_siw=1 ./check -q srp/005
> 
> srp/015 seem to be dedicated to siw testing. It selects siw if available.
> I think this is how Bart found it.
> Unfortunately, for some reason I am not aware of, testing defaults to
> rxe only for the other tests. Maybe at least the helper should
> talk about this hidden option.

Originally only test srp/015 selected siw. Yi Zhang added support for
running all SRP tests with the siw driver. See also blktests commit
d23c3aa0c1c0 ("common/multipath-over-rdma: allow to set use_siw"). How
about submitting a documentation patch to the blktests project?

Thanks,

Bart.

  reply	other threads:[~2021-09-18  2:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHj4cs9Rzte5zbgy7o158m7JA8dbSEpxy5oR-+K0NQCK1gxG=Q@mail.gmail.com>
2021-09-16 19:36 ` Issus with blktest/srp on 5.15-rc1 and rdma_rxe Bernard Metzler
2021-09-16 22:21   ` Robert Pearson
2021-09-17  8:23     ` Bernard Metzler
2021-09-18  2:56       ` Bart Van Assche [this message]
2021-09-18 12:15         ` Yi Zhang
2021-09-21 20:08       ` Still issues with blktest/srp on 5.15-rc1 and software rdma providers Bernard Metzler
2021-09-21 20:16         ` Bart Van Assche
2021-09-17  8:15   ` Re: Issus with blktest/srp on 5.15-rc1 and rdma_rxe Bernard Metzler

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=79755291-a36f-535c-03b8-73178f80ca5e@acm.org \
    --to=bvanassche@acm.org \
    --cc=BMT@zurich.ibm.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yi.zhang@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).