| To: | tharbaugh@xxxxxxxx |
|---|---|
| Subject: | abysmal e1000 performance (DITR) |
| From: | Robert Olsson <Robert.Olsson@xxxxxxxxxxx> |
| Date: | Mon, 7 Jun 2004 16:57:30 +0200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <1085700138.30156.1322.camel@tubarao> |
| References: | <1085700138.30156.1322.camel@tubarao> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Thayne Harbaugh writes:
> This is a patch to include system load when calculating the DITR. It
> only allows the diff/goc ratio to factor into the DITR when the 1 minute
> load average is above .50. It appears to work quite well and prevents
> throttling when the load is below .50 and allows throttling when the
> load is in excess of .50.
Hello!
The experience we had from decorrelating network traffic for use with variable
interrupt delays etc was that no average based scheme worked at the packet
resolution we wanted.
The only useful measure we found was using the number of packets received
on the RX-ring. You see this used in tulip driver to get a dynamic RX
interrupt delay.
Cheers.
--ro
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] common code for generating tcp_info, Joe Perches |
|---|---|
| Next by Date: | Re: [PATCH] common code for generating tcp_info, Stephen Hemminger |
| Previous by Thread: | in-driver QoS, Vladimir Kondratiev |
| Next by Thread: | Re: abysmal e1000 performance (DITR), Thayne Harbaugh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |