public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org"
	<benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Subject: Re: [PATCH] Add rdma service for kernel boot support
Date: Thu, 13 Jul 2017 16:51:27 -0600	[thread overview]
Message-ID: <20170713225127.GA25543@obsidianresearch.com> (raw)
In-Reply-To: <1499985913.2740.26.camel-Sjgp3cTcYWE@public.gmane.org>

On Thu, Jul 13, 2017 at 10:45:14PM +0000, Bart Van Assche wrote:

> Users who want to enable RDMA target functionality probably will know the
> names of the kernel modules that provide such functionality. On Debian
> systems the names of these kernel modules can e.g. be added to /etc/modules.
> However, I'm not sure all distro's have an equivalent of the /etc/modules
> file.

systemd supports /etc/modules-load.d/ as a built in, some distros will
symlink ../modules.conf to that directory, but these days dropping a
file in /etc/modules-load.d/ is pretty safe.

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-07-13 22:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 17:20 [PATCH] Add rdma service for kernel boot support Benjamin Drung
     [not found] ` <20170713172057.25411-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-13 17:48   ` Bart Van Assche
     [not found]     ` <1499968101.2740.10.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-13 18:20       ` Jason Gunthorpe
     [not found]         ` <20170713182018.GE11069-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-13 18:33           ` Bart Van Assche
     [not found]             ` <1499970786.2740.17.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-13 22:15               ` Jason Gunthorpe
     [not found]                 ` <20170713221520.GA10088-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-13 22:36                   ` Bart Van Assche
     [not found]                     ` <1499985409.2740.24.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-13 22:41                       ` Jason Gunthorpe
     [not found]                         ` <20170713224137.GA24689-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-13 22:45                           ` Bart Van Assche
     [not found]                             ` <1499985913.2740.26.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-13 22:51                               ` Jason Gunthorpe [this message]
2017-07-14 10:08                   ` Benjamin Drung
     [not found]                     ` <1500026921.3563.27.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-14 10:18                       ` Benjamin Drung
2017-07-14 15:55                       ` Jason Gunthorpe
     [not found]                         ` <20170714155544.GA25760-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-14 16:23                           ` Benjamin Drung
     [not found]                             ` <1500049393.3563.42.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-14 16:40                               ` Jason Gunthorpe
     [not found]                                 ` <20170714164029.GA9942-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-20  9:04                                   ` Benjamin Drung
     [not found]                                     ` <1500541450.4226.5.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-21  2:45                                       ` Jason Gunthorpe

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=20170713225127.GA25543@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org \
    --cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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