From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Joe Perches <joe@perches.com>,
jtoppins@redhat.com, David Miller <davem@davemloft.net>,
michael.j.dilmore@gmail.com
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add printk for bonding module packets_per_slave parameter
Date: Tue, 13 Jun 2017 20:53:40 +0300 [thread overview]
Message-ID: <1e319c81-0a39-0b1e-75ff-96eb7a5963df@cumulusnetworks.com> (raw)
In-Reply-To: <1497373252.18751.19.camel@perches.com>
On 13/06/17 20:00, Joe Perches wrote:
> On Tue, 2017-06-13 at 12:42 -0400, Jonathan Toppins wrote:
>> On 06/13/2017 12:21 PM, Joe Perches wrote:
>>> On Tue, 2017-06-13 at 11:34 -0400, David Miller wrote:
>>>> From: Michael Dilmore <michael.j.dilmore@gmail.com>
>>>> Date: Tue, 13 Jun 2017 14:42:46 +0100
>>>>
>>>>> The packets per slave parameter used by round robin mode does not have a printk debug
>>>>> message in its set function in bond_options.c. Adding such a function would aid debugging
>>>>> of round-robin mode and allow the user to more easily verify that the parameter has been
>>>>> set correctly. I should add that I'm motivated by my own experience here - it's not
>>>>> obvious from output of tools such as wireshark and ifstat that the parameter is working
>>>>> correctly, and with the differences in bonding configuration across different distributions,
>>>>> it would have been comforting to see this output.
> []
>>>> You can verify things by simplying reading the value back.
>>>>
>>>> If every parameter emitted a kernel log message, it would be
>>>> unreadable.
>>>>
>>>> I'm not applying this, sorry.
>>>
>>> I agree. Noisy logging output is not good.
>>>
>>> Perhaps a general conversion of the dozens
>>> of existing netdev_info uses in this file to
>>> netdev_dbg and adding this at netdev_dbg is
>>> appropriate.
>>
>> In general I agree. The few times I have debugged bonds, I always ended
>> up enabling debug prinks anyway. I don't see a problem moving these to
>> debug as well.
>>
>> Adding nik whom converted a lot of this code to common paths for input.
>
> If Nikolay agrees with the conversion, it's trivial.
> Please submit it. I did it just for reference.
>
> Stylistic nits about the existing file:
>
> There are some inconsistencies in pr_info/pr_err uses
> with invalid inputs.
>
> It would also be nicer if the forward static declarations
> were removed and the static definitions reordered.
>
Agreed, there are many ways to extract the values.
next prev parent reply other threads:[~2017-06-13 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 13:42 Michael Dilmore
2017-06-13 15:34 ` David Miller
2017-06-13 16:21 ` Joe Perches
2017-06-13 16:42 ` Jonathan Toppins
2017-06-13 17:00 ` Joe Perches
2017-06-13 17:53 ` Nikolay Aleksandrov [this message]
2017-06-13 16:46 ` David Miller
2017-06-13 21:18 ` kbuild test robot
2017-06-13 23:12 ` kbuild test robot
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=1e319c81-0a39-0b1e-75ff-96eb7a5963df@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=joe@perches.com \
--cc=jtoppins@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.j.dilmore@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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
all inboxes | Powered by JetHome®