ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Developing across multiple areas of the kernel
Date: Fri, 14 Jul 2017 18:35:44 +0300	[thread overview]
Message-ID: <20170714153544.GE1528@mtr-leonro.local> (raw)
In-Reply-To: <20170714141057.GC21743@lunn.ch>

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

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.

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
e.t.c.

>
>     Andrew

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-07-14 15:35 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 [this message]
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

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=20170714153544.GE1528@mtr-leonro.local \
    --to=leon@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andrew@lunn.ch \
    --cc=ksummit-discuss@lists.linuxfoundation.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