[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190412193024.GB4690@ziepe.ca>
Date: Fri, 12 Apr 2019 16:30:24 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Parav Pandit <parav@...lanox.com>
Cc: Leon Romanovsky <leon@...nel.org>,
Doug Ledford <dledford@...hat.com>,
Steve Wise <swise@...ngridcomputing.com>,
HÃ¥kon Bugge <haakon.bugge@...cle.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RDMA/cma: Make CM response timeout and # CM retries
configurable
On Mon, Mar 04, 2019 at 06:27:26AM +0000, Parav Pandit wrote:
> I think we should use rdma_nl_register(RDMA_NL_RDMA_CM, cma_cb_table) which was removed as part of ID stats removal.
> Because of below reasons.
> 1. rdma netlink command auto loads the module
This is probably the best argument to stay away from sysctl for module
parameters.. It is tricky to make sure the rdma module is loaded
before sysctl runs in boot, and I don't think sysctl autoloads missing
modules, or somehow copes with dynamic module loading, does it?
To that end we should probably have the entire sysctl configurable
available in netlink
Jason
Powered by blists - more mailing lists