[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0CA0A16855646F4FA96D25A158E299D606FFE7FF@SDCEXCHANGE01.ad.amcc.com>
Date: Mon, 21 Sep 2009 16:49:26 -0700
From: "Prodyut Hazarika" <phazarika@...c.com>
To: "Benjamin Herrenschmidt" <benh@...nel.crashing.org>
Cc: <netdev@...r.kernel.org>, "Feng Kan" <fkan@...c.com>,
"Loc Ho" <lho@...c.com>, "Victor Gallardo" <vgallardo@...c.com>,
<bhutchings@...arflare.com>, <linuxppc-dev@...ts.ozlabs.org>,
<davem@...emloft.net>, <jwboyer@...ux.vnet.ibm.com>,
<lada.podivin@...il.com>
Subject: RE: [PATCH 1/2] ibm_newemac: Add Support for MAL Interrupt Coalescing
Hi Ben,
Thanks for your comments.
> What happens if we build a kernel that is supposed to boot with two
> different variants of 405 or 440 ?
We cannot build a kernel with H/W Interrupt coalescing other than in
405EX/460EX/GT.
This is controlled via KConfig (config IBM_NEW_EMAC_INTR_COALESCE
depends on IBM_NEW_EMAC && (460EX || 460GT || 405EX))
Is this approach acceptable (via Kconfig)?
> There are existing mechanisms via ethtool to configure coalescing. You
> should hookup onto these.
I will start looking at the ethtool options
Thanks
Prodyut
--
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