Buildroot Archive on 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: Mon, 19 Sep 2022 12:48:40 +0200	[thread overview]
Message-ID: <20220919124840.0f8d8b4b@windsurf> (raw)
In-Reply-To: <3a565e425e1bb39439434e1681918682@free.fr>

Hello Julien,

On Mon, 19 Sep 2022 00:38:27 +0200
Julien Olivain <ju.o@free.fr> wrote:


> >> +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?  
> 
> Yes, I considered <pkg>_LINUX_CONFIG_FIXUPS but decided not to use it.
> This fragment is really an example with the rdma_rxe driver. The
> rdma-core package could be used with any other Kernel InfiniBand
> driver. The reason I picked this one, is it's a purely software
> implementation and does not require any specific hardware to test.
> 
> The only Kernel config that could always be enabled would be
> CONFIG_INFINIBAND to enable the core support. The value would be
> limited as it would be an empty shell since no other driver/options
> would be enabled.
> 
> I could then enable a bit more kernel configs, but I think this would
> go against the Buildroot philosophy (which I could summarize as
> "Buildroot only enables the mandatory things, the user enables only
> what he/she needs/wants").
> 
> I used the word "example" for that purpose. If needed, I can clarify
> even more in the text.

Then I think there is no need to provide this example, just put the
kernel config fragment as an artifact together with the runtime test.

> >> +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?  
> 
> Yes, the reasons are:
> - Those are indeed needed for a specific use cases,
> - Those are not mandatory dependencies (neither for build nor runtime).

OK. Then indeed, suggesting that they can be relevant (and in which
case) in the Config.in help text would be useful.

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-19 10:48 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
2022-09-18 22:38   ` Julien Olivain
2022-09-19 10:48     ` Thomas Petazzoni [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=20220919124840.0f8d8b4b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox