----- Original Message ----- From: "Benjamin LaHaise" <[EMAIL PROTECTED]> To: "JaniD++" <[EMAIL PROTECTED]> Cc: <netdev@vger.kernel.org> Sent: Friday, December 02, 2005 10:26 PM Subject: Re: e1000 performance question.
> On Fri, Dec 02, 2005 at 09:23:33PM +0100, JaniD++ wrote: > > I have 4 HW-equal disk nodes, what i use with NBD. > > > When i try to get the top performance, i seriously found the network as the > > bottleneck. > > What motherboard are you using? On my test box I am able to get 100MB/s > reads over the network with nbd (granted that is with the file cached on > the server). Intel SE7520AF2 in the concentrator. The xeon boards card performance is good. I have problem with the nbd-servers 32bit e1000 card. > > > 169: 18907824 0 IO-APIC-level libata, eth0 > > Shared interrupts? Bad... Yes, i know, but i think it is no problem: The eth0 in this box is only use to boot up nfsroot. ;-) The traffic is only on the eth1. In the nbd-servers i use Abit IS7 board, and i cannot split this irq. > > > 177: 1144300306 0 IO-APIC-level eth1 > > Is eth1 the e1000? Try binding it to the second CPU by doing an > > echo >/proc/irq/177 2 Yes, i think too, it is good idea! I have two problem about this. 1. The echo 2 >/proc/irq/177/smp_affinity has no effect at all. :( Looks like read-only file... (?) ... and i dont know why! 2. this is only HT, not dual CPU on the nodes. But i think this can help a little..... > > The e1000 driver also has several tunable options for its various > features. See drivers/net/e1000/e1000_param.c. Disabling interrupt > rate throttling might help. OK, i will try it! This can cause the long ping time? Thanks! Cheers, Janos > > -ben > -- > "You know, I've seen some crystals do some pretty trippy shit, man." > Don't Email: <[EMAIL PROTECTED]>. > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
