From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Omar Sandoval <osandov@fb.com>, linux-block@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add an SRP test for the SoftiWARP driver
Date: Thu, 19 Dec 2019 13:47:35 -0800 [thread overview]
Message-ID: <20191219214735.GA830111@vader> (raw)
In-Reply-To: <20191213143232.29899-1-bvanassche@acm.org>
On Fri, Dec 13, 2019 at 09:32:28AM -0500, Bart Van Assche wrote:
> Hi Omar,
>
> Recently a new low-level RDMA driver went upstream, namely the SoftiWARP
> driver. That driver implements RDMA over TCP. Support has been added in the
> SRP initiator and target drivers for iWARP. This patch series adds a test
> for SRP over SoftiWARP. Please consider integration of this patch series in
> the official blktests repository.
>
> Thanks,
>
> Bart.
>
> Changes compared to v1:
> - Only run the new test if the kernel version is at least 5.5 (the version in
> which iWARP support was added to the SRP drivers) and if "rdma link" is
> supported.
Hi, Bart,
Is there no way to detect this feature other than checking the kernel
version?
Thanks.
next prev parent reply other threads:[~2019-12-19 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 14:32 [PATCH v2 0/4] Add an SRP test for the SoftiWARP driver Bart Van Assche
2019-12-13 14:32 ` [PATCH v2 1/4] common/multipath-over-rdma: Fix expand_ipv6_addr() Bart Van Assche
2019-12-13 14:32 ` [PATCH v2 2/4] common/multipath-over-rdma: Rename two functions Bart Van Assche
2019-12-13 14:32 ` [PATCH v2 3/4] common/multipath-over-rdma, tests/srp: Make it easy to use siw instead of rdma_rxe Bart Van Assche
2019-12-13 14:32 ` [PATCH v2 4/4] tests/srp/015: Add a test that uses the SoftiWARP (siw) driver Bart Van Assche
2019-12-19 21:47 ` Omar Sandoval [this message]
2019-12-19 22:04 ` [PATCH v2 0/4] Add an SRP test for the SoftiWARP driver Bart Van Assche
2019-12-19 22:43 ` Omar Sandoval
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=20191219214735.GA830111@vader \
--to=osandov@osandov.com \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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