Thank You Emil. I appreciate you help.
On Thu, Mar 5, 2009 at 7:12 PM, Tantilov, Emil S
<[email protected]>wrote:
> If your change is correct you will see a high number of interrupts/sec (for
> example when measured with netperf using the RR tests or when transmitting
> small packets). With interrupt throttling enabled your int/sec will be
> capped at either 8k or 20k int/sec (depending on the version of e1000 you're
> using).
>
> Also on a newer version e1000 you can use ethtool to change ITR on a fly
> using ethtool -c/C to check/modify the rx-usecs parameter.
>
> For example to cap int/sec at 8k:
> ethtool -C rx-usecs 125
>
> (100000/125 = 8000)
>
> Thanks,
> Emil
>
> -----Original Message-----
> From: Ezra Taylor [mailto:[email protected]]
> Sent: Thursday, March 05, 2009 3:51 PM
> To: [email protected]
> Subject: [E1000-devel] compiling the e1000 driver statically.
>
> Hello all:
> First, I would like to apologize if this is the wrong place to
> ask this question. Here it goes. We are running Kernels with drivers we
> only need. The driver are compiled statically into the Linux Kernel. I
> was
> told recently to disable interrupt throttling to test its impact on our
> systems. The file I edited was _param.c. After editing this file, I
> recompiled the Kernel with no known issues. How can I tell that the change
> I made took affect? I would like to thank you guys for your hard work and
> your help.
>
> --
> Ezra Taylor
>
--
Ezra Taylor
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
