From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "andrew@lunn.ch" <andrew@lunn.ch>, "leon@kernel.org" <leon@kernel.org>
Cc: "James.Bottomley@hansenpartnership.com"
<James.Bottomley@hansenpartnership.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel
Date: Fri, 14 Jul 2017 16:28:04 +0000 [thread overview]
Message-ID: <1500049683.2662.6.camel@wdc.com> (raw)
In-Reply-To: <20170714161824.GJ21743@lunn.ch>
On Fri, 2017-07-14 at 18:18 +0200, Andrew Lunn wrote:
> On Fri, Jul 14, 2017 at 06:35:44PM +0300, Leon Romanovsky wrote:
> > On Fri, Jul 14, 2017 at 04:10:57PM +0200, Andrew Lunn wrote:
> > > > The difference in maintainers style between netdev and RDMA causes to have long queue
> > > > (100+) of patches posted to the ML [2], which are not cross-checked in various CIs.
> > >
> > > It is possible to get 0-day to run against any arbitrary git tree, if
> > > you ask nicely. If same is true for the kernel-ci project. So if you
> > > are willing to do the merge work, you can get it tested.
> >
> > 0-day is checking my tree, so it is not the problem.
> >
> > I don't see how kernel-ci can help me, because RDMA requires special
> > hardware to run it and it usually requires more than two endpoints (servers)
> > connected together.
>
> kernel-ci are happy to receive hardware. I've sent them boards in the
> past which have been added to their test farm. Kernel-ci is mostly
> about boot testing, but they do do some tests post boot. So if you can
> supply tests as well, they may run them for you.
>
> > My problem is related to changes in other trees for example netdev, which
> > can break RDMA functionality.
> >
> > Technology wise, there are:
> > 1. RoCE - RDMA over Converged Ethernet - netdev is below RDMA
> > 2. IPoIB - IP over Infiniband - netdev is above RDMA
> > 3. HFI-VNIC - Ethernet over OmniPath - netdev is above RDMA
> > 4. iWARP - RDMA over IP networks
>
> How much of this do you already have automated test for? You can also
> setup your own test farm, using the kernels kernel-ci builds.
Hello Andrew,
The srp-test software is fully automated. It requires IB hardware today but does
not require a second server because it uses IB loopback. As soon as I have the time
I will add RoCE support to the upstream SRP initiator and target drivers such that
these tests can be run on top of Ethernet hardware. Please let me know if you would
like to start using this software and if you need help. See also
https://github.com/bvanassche/srp-test.
Bart.
prev parent reply other threads:[~2017-07-14 16:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:01 Kees Cook
2017-06-29 13:39 ` Christoph Hellwig
2017-06-30 13:02 ` Daniel Vetter
2017-06-29 16:36 ` James Bottomley
2017-06-29 16:51 ` Kees Cook
2017-06-29 17:42 ` James Bottomley
2017-06-29 17:52 ` Kees Cook
2017-06-29 18:20 ` Luis R. Rodriguez
2017-06-29 19:07 ` Linus Torvalds
2017-06-29 20:16 ` Kees Cook
2017-06-29 20:27 ` Stephen Rothwell
2017-07-14 4:04 ` Leon Romanovsky
2017-07-14 9:54 ` Greg KH
2017-07-14 10:29 ` Leon Romanovsky
2017-07-14 14:10 ` Andrew Lunn
2017-07-14 15:05 ` Mark Brown
2017-07-14 15:51 ` Leon Romanovsky
2017-07-14 16:20 ` Mark Brown
2017-07-14 15:35 ` Leon Romanovsky
2017-07-14 15:43 ` James Bottomley
2017-07-14 16:08 ` Leon Romanovsky
2017-07-14 16:18 ` Andrew Lunn
2017-07-14 16:28 ` Bart Van Assche [this message]
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=1500049683.2662.6.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andrew@lunn.ch \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=leon@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