Re: e100 latency, cpu cycle saver and e1000...

Zwane Mwaikambo (zwane@linuxpower.ca)
Wed, 21 May 2003 18:50:08 -0400 (EDT)


On Wed, 21 May 2003, Paul Rolland wrote:

> Correct, machines are not idle... but
> - they are doing globally the same work,
> - this behavior is something I can reproduce test after test, since
> I've started this morning...
>
> I started using that because IP1 was exhibiting high latency yesterday
> 'til I rebooted it, and since it is working quite fine...
> Of course, I can reboot also IP2, but I'd like to understand why
> and how to avoid it later...

One thing you can do to reduce packet handling latency (at the cost of
CPU) with both the e1000 is drop down the RX Delay Interrupt timers, ditto
for the Tx Delay. The hardware delays in increments of 1.024ms

Zwane

-- 
function.linuxpower.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/