netdev
[Top] [All Lists]

Re: Info: NAPI performance at "low" loads

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: Info: NAPI performance at "low" loads
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: 18 Sep 2002 22:15:27 +0100
Cc: ebiederm@xxxxxxxxxxxx, hadi@xxxxxxxxxx, akpm@xxxxxxxxx, manfred@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20020918.134630.127509858.davem@xxxxxxxxxx>
References: <m1hegnky2h.fsf@xxxxxxxxxxxxxxxxxxx> <20020918.132334.102949210.davem@xxxxxxxxxx> <1032381789.20498.151.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20020918.134630.127509858.davem@xxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Wed, 2002-09-18 at 21:46, David S. Miller wrote:
>    From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
>    Date: 18 Sep 2002 21:43:09 +0100
>    
>    The inb timing depends on the PCI bus. If you want proof set a Matrox
>    G400 into no pci retry mode, run a large X load at it and time some inbs
>    you should be able to get to about 100 milliseconds for an inb to
>    execute
>    
> Matrox isn't using inb/outb instructions to IO space, it is being
> accessed by X using MEM space which is done using normal load and
> store instructions on x86 after the card is mmap()'d into user space.

It doesnt matter what XFree86 is doing. Thats just to load the PCI bus
and jam it up to prove the point. It'll change your inb timing


<Prev in Thread] Current Thread [Next in Thread>