| To: | alan@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Info: NAPI performance at "low" loads |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Wed, 18 Sep 2002 13:46:30 -0700 (PDT) |
| Cc: | ebiederm@xxxxxxxxxxxx, hadi@xxxxxxxxxx, akpm@xxxxxxxxx, manfred@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <1032381789.20498.151.camel@irongate.swansea.linux.org.uk> |
| References: | <m1hegnky2h.fsf@frodo.biederman.org> <20020918.132334.102949210.davem@redhat.com> <1032381789.20498.151.camel@irongate.swansea.linux.org.uk> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Info: NAPI performance at "low" loads, Alan Cox |
|---|---|
| Next by Date: | Re: Info: NAPI performance at "low" loads, Alan Cox |
| Previous by Thread: | Re: Info: NAPI performance at "low" loads, Alan Cox |
| Next by Thread: | Re: Info: NAPI performance at "low" loads, Alan Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |