netdev - Re: [PATCH net-next v2 00/12] cdc_ncm: add buffer tuning and stats using ethtool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 18 May 2014 11:57:05 +0200 (CEST)
From:	Enrico Mioso <mrkiko.rs@...il.com>
To:	Bjørn Mork <bjorn@...k.no>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-usb@...r.kernel.org, alexey.orishko@...il.com,
	oliver@...kum.org, David.Laight@...lab.com
Subject: Re: [PATCH net-next v2 00/12] cdc_ncm: add buffer tuning and stats
 using ethtool

Or a set of module parameters, allowing them to be tuned at run-time via (e.g.) 
the param directory of the module in sysfs?
Yes, I imagine it's not the best solution.

On Sun, 18 May 2014, Peter Stuge wrote:

==Date: Sun, 18 May 2014 03:19:17
==From: Peter Stuge <peter@...ge.se>
==Reply-To: Bjørn Mork <bjorn@...k.no>, David Miller <davem@...emloft.net>,
==    netdev@...r.kernel.org, linux-usb@...r.kernel.org,
==    alexey.orishko@...il.com, oliver@...kum.org, mrkiko.rs@...il.com,
==    David.Laight@...lab.com
==To: Bjørn Mork <bjorn@...k.no>
==Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
==    linux-usb@...r.kernel.org, alexey.orishko@...il.com, oliver@...kum.org,
==    mrkiko.rs@...il.com, David.Laight@...lab.com
==Subject: Re: [PATCH net-next v2 00/12] cdc_ncm: add buffer tuning and stats
==    using ethtool
==
==Bjørn Mork wrote:
==> > Just make doubly sure that you will be ok, for a long time, with using
==> > the ethtool coalescing interface for configuring this because you'll
==> > really be stuck with this forever.
==> 
==> Yes, I am painfull aware of that.  So I was hoping someone would jump at
==> this and say something like "That's not the way to do it.  Use the foo
==> interface instead. It's made for stuff like this".
==
==sysfs?
==
==
==//Peter
==