... to cacheing and what not). i wouldn't think that you could tune out rotational latency. 8.4ms is pretty much forever when you're counting nanoseconds. since aoe can do wirespeed (120ms/s) on typical physical gige chipsets i would think it would have no trouble keeping up with spinning media. especially when not handicapped by having to actually stuff bits through a...

... hardware due to cacheing and what not). i wouldn't think that you could tune out rotational latency. 8.4ms is pretty much forever when you're counting nanoseconds. since aoe can do wirespeed (120ms/s) on typical physical gige chipsets i would think it would have no trouble keeping up with spinning media. especially when not handicapped by having to actually stuff bits through a phy....

...on the target side provisioned and you are doing 100%% random 512b writes, then yeah, it's gonna be kinda slow. If you were to do 100%% cache read or write, you can easily run wirespeed using 2.05 assuming you've got a decent Intel server NIC (using other targets anyway). How many spindles on the backend? What type of workload (read%%, sequential/random%%, request size, etc)? ~...

... 217 eth0: Tigon3 [partno(BCM95705A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:e0:81:5c:35:9c eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1] eth0: dma_rwctrl[763f0000] dma_mask[64-bit] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.49. ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23 GSI 17 sharing vector 0xE1 and IRQ...