[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20100322.182827.180417968.davem@davemloft.net>
Date: Mon, 22 Mar 2010 18:28:27 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jeffrey.t.kirsher@...el.com
Cc: netdev@...r.kernel.org, gospo@...hat.com,
nicholasx.d.nunley@...el.com
Subject: Re: [net-next-2.6 PATCH] igb: add IntMode module parameter
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Mon, 22 Mar 2010 17:06:20 -0700
> From: Nick Nunley <nicholasx.d.nunley@...el.com>
>
> This patch adds the IntMode module parameter to igb. This
> allows user selection of interrupt mode (MSI-X, MSI, legacy)
> on driver load.
>
> Signed-off-by: Nicholas Nunley <nicholasx.d.nunley@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
And IGB is special and needs this for what reason?
If there are real interrupt issues then:
1) Diagnosing via verification of the problem can be simply performed
by asking the user to pass the generic kernel boot option to
globally disable MSI and friends.
2) Specifically disabling it for buggy parts belongs in the
driver or in the PCI quirk tables.
So from just about any angle, this module option makes no sense.
So I'm not applying it, sorry.
--
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