From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, nguyendo@us.ibm.com,
jallen@linux.vnet.ibm.com, brking@linux.vnet.ibm.com,
nfont@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next] Driver for IBM System i/p VNIC protocol
Date: Mon, 7 Dec 2015 12:50:00 -0600 [thread overview]
Message-ID: <5665D4D8.7010206@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151205.222551.512793392902323297.davem@davemloft.net>
On 12/05/2015 09:25 PM, David Miller wrote:
> From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
> Date: Fri, 4 Dec 2015 11:49:46 -0600
>
>> +static int ibmvnic_buffs_per_pool = IBMVNIC_BUFFS_PER_POOL;
>> +module_param(ibmvnic_buffs_per_pool, int, S_IRUGO);
>> +MODULE_PARM_DESC(ibmvnic_buffs_per_pool,
>> + "IBMVNIC number of buffers per rx pool");
> Please do not use module parameters for settings that effect
> the basic operation of the driver.
Hi. Thanks for you feedback. Could you clarify on what constitutes basic operation? I just want to be sure if we should remove the other module parameters or just this one in particular?
>
> Instead use facilities that are generic and provide the same
> user interface for all networking drivers, such as ethtool.
Is it possible to change driver settings like this with ethtool? Would adding an interface in sysfs to change this setting be acceptable?
>
> Otherwise users would need to learn a different way to configure the
> same thing on different devices, which is not acceptable.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2015-12-07 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:49 [PATCH net-next] Driver for IBM System i/p VNIC protocol Thomas Falcon
2015-12-06 3:25 ` David Miller
2015-12-07 18:50 ` Thomas Falcon [this message]
2015-12-07 19:45 ` David Miller
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=5665D4D8.7010206@linux.vnet.ibm.com \
--to=tlfalcon@linux.vnet.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=jallen@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=nguyendo@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).