[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111115143231.454f612a@s6510.linuxnetplumber.net>
Date: Tue, 15 Nov 2011 14:32:31 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: David Decotigny <david.decotigny@...gle.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Ian Campbell <ian.campbell@...rix.com>,
Eric Dumazet <eric.dumazet@...il.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Ben Hutchings <bhutchings@...arflare.com>,
Jiri Pirko <jpirko@...hat.com>, Joe Perches <joe@...ches.com>,
Szymon Janc <szymon@...c.net.pl>,
Richard Jones <rick.jones2@...com>,
Ayaz Abdulla <AAbdulla@...dia.com>
Subject: Re: [PATCH net-next v4 4/8] forcedeth: expose module parameters in
/sys/module
On Tue, 15 Nov 2011 11:25:37 -0800
David Decotigny <david.decotigny@...gle.com> wrote:
> +module_param(optimization_mode, int, S_IRUGO);
> MODULE_PARM_DESC(optimization_mode, "In throughput mode (0), every tx & rx packet will generate an interrupt. In CPU mode (1), interrupts are controlled by a timer. In dynamic mode (2), the mode toggles between throughput and CPU mode based on network load.");
Probably the original developer (or marketing data sheet), thought this was some
unique feature of the hardware. But most devices have this already.
This driver should just implement proper control irq coalescing control via ethtool
and get rid of the silly module parameter.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists