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@xxxxxxxx> ==Reply-To: Bjørn Mork <bjorn@xxxxxxx>, David Miller <davem@xxxxxxxxxxxxx>, == netdev@xxxxxxxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx, == alexey.orishko@xxxxxxxxx, oliver@xxxxxxxxxx, mrkiko.rs@xxxxxxxxx, == David.Laight@xxxxxxxxxx ==To: Bjørn Mork <bjorn@xxxxxxx> ==Cc: David Miller <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, == linux-usb@xxxxxxxxxxxxxxx, alexey.orishko@xxxxxxxxx, oliver@xxxxxxxxxx, == mrkiko.rs@xxxxxxxxx, David.Laight@xxxxxxxxxx ==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 ==
