All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 1/1] package/rdma-core: new package
Date: Sat, 17 Sep 2022 22:49:34 +0200	[thread overview]
Message-ID: <20220917224934.01388da4@windsurf> (raw)
In-Reply-To: <20220821160143.16646-1-ju.o@free.fr>

Hello Julien,

On Sun, 21 Aug 2022 18:01:43 +0200
Julien Olivain <ju.o@free.fr> wrote:

> This is the userspace components for the Linux Kernel's
> drivers/infiniband subsystem.
> 
> https://github.com/linux-rdma/rdma-core
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>

Thanks for this patch. It looks really good. I have just a few
questions and one super minor comment, see below.

> diff --git a/package/rdma-core/readme.txt b/package/rdma-core/readme.txt
> new file mode 100644
> index 0000000000..4f90720ca3
> --- /dev/null
> +++ b/package/rdma-core/readme.txt
> @@ -0,0 +1,74 @@
> +Testing rdma-core userspace tools
> +=================================
> +
> +Testing rdma-core using Linux software RoCE implementation:
> +https://en.wikipedia.org/wiki/RDMA_over_Converged_Ethernet
> +
> +Using two systems with working TCP/IP conficutation, for example:

                                         ^^^^^^^ minor typo here

> +Kernel configuration
> +--------------------
> +
> +The Linux Kernel needs some Infiniband configuration. In this example
> +the kernel "rdma_rxe" driver is needed (CONFIG_RDMA_RXE=y). See the
> +example fragment file provided:
> +
> +    package/rdma-core/linux-rdma.fragment

Did you consider using the <pkg>_LINUX_CONFIG_FIXUPS variable instead?
This would make sure these configuration options are always enabled in
the kernel. Or is your fragment just an example?

> +Buildroot package configuration
> +-------------------------------
> +
> +For setting up a software RoCE link, the "rdma" program is needed. It
> +is provided by the "iproute2" package, when "libmnl" is also
> +selected. Make sure to have in your Buildroot configuration:
> +
> +    BR2_PACKAGE_IPROUTE2=y
> +    BR2_PACKAGE_LIBMNL=y
> +    BR2_PACKAGE_RDMA_CORE=y

Then is there a reason to not select iproute2 and libmnl? Or is it just
that they are needed only for specific use cases?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-17 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 16:01 [Buildroot] [PATCH next 1/1] package/rdma-core: new package Julien Olivain
2022-09-17 20:49 ` Thomas Petazzoni [this message]
2022-09-18 22:38   ` Julien Olivain
2022-09-19 10:48     ` Thomas Petazzoni

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=20220917224934.01388da4@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.