More performance for the TCP stack by using additional hardware chip on NIC
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 42 lines · Willy Tarreau
Hello !
Quoted 15 lines · Avi Kivity
Quoted 8 lines · Arjan van de Ven
Quoted 6 lines · Andreas Hartmann
Hello!
Alacritech developed a new chip for NIC's
(http://www.alacritech.com/html/tech_review.html), which makes it possible to take away the TCP stack from the host CPU. Therefore, the host CPU has more performance for the applications according Alacritech.Quoted 5 lines
there are very many good reasons why this for linux is not the right solution, including the fact that the linux tcp/ip stack already is quite fast so the "gains" achieved aren't that stellar as the gains you get when comparing to windows.
Quoted 4 lines
TOEs can remove the data copy on receive. In some applications (notably storage), where the application does not touch most of the data, this is a significant advantage that cannot be achieved in a software-only solution.
Well, if the application does not touch most of the data, either it is playing as a relay, and the data will at least have to be copied, or it will play as a client or server which reads from/writes to disk, and in this case, I wonder how the NIC will send its writes directly to the disk controller without some help.
What worries me with those NICs is that you have no control on the TCP stack. You often have to disable the acceleration when you want to insert even 1 firewall rule, use policy routing or even do a simple anti-spoofing check. It is exactly like the routers which do many things in hardware at wire speed, but jump to snail speed when you enable any advanced feature.
Quoted 6 lines
Quoted 5 lines
Also these types of solution always add quite a bit of overhead to connection setup/teardown making it actually a *loss* for the "many short connections" types of workloads. Now guess which things certain benchmarks use, and guess what real world servers do :)
Quoted 6 lines
Quoted 1 line
again, this depends on the application.
The speed itself depends on the application. An application which goal is to achieve 10 Gbps needs to be written with this goal in mind from start, and needs fine usage of the kernel internals, and even sometimes good knowledge of the hardware itself.
Alacritech says, the hardware solution would make it very easy for the application, because _every_ application would gain, without considering the hardware it runs on itself. These are things which CEO's like to hear
- because they think, they could save time and money during development of the application.
I don't think that it must be a problem, that on the hardware TCP stack doesn't run any filter or other additional functions, because machines (often clusters) with high workloads usually run on dedicated servers with other dedicated firewall machines in front of.
I think it would be good to support this hardware, because the user can decide afterwards (after testing), which is the best choice for his specific application and workload.
Kind regards,
Andreas Hartmann
Quoted 6 lines · Andreas Hartmann
Quoted 5 lines · Willy Tarreau
Well, if the application does not touch most of the data, either it is playing as a relay, and the data will at least have to be copied, or it will play as a client or server which reads from/writes to disk, and in this case, I wonder how the NIC will send its writes directly to the disk controller without some help.
If both NIC and disk is clever enough, they can both use DMA:
NIC ==dma==> RAM ==dma==> DISK
without CPU needing to ever touch the bulk of data.
Quoted 6 lines
Quoted 6 lines
What worries me with those NICs is that you have no control on the TCP stack. You often have to disable the acceleration when you want to insert even 1 firewall rule, use policy routing or even do a simple anti-spoofing check. It is exactly like the routers which do many things in hardware at wire speed, but jump to snail speed when you enable any advanced feature.
Yes. This is why TCP offload is a buzzword mostly. Anybody with real experience on this?
Quoted 5 lines
Alacritech says, the hardware solution would make it very easy for the application, because _every_ application would gain, without considering the hardware it runs on itself. These are things which CEO's like to hear
- because they think, they could save time and money during development of the application.
Most probably marketspeak.
Quoted 4 lines
I don't think that it must be a problem, that on the hardware TCP stack doesn't run any filter or other additional functions, because machines (often clusters) with high workloads usually run on dedicated servers with other dedicated firewall machines in front of.
If you put firewall machine in front of your 10GigE server, you are killing its performance.
Quoted 3 lines
I think it would be good to support this hardware, because the user can decide afterwards (after testing), which is the best choice for his specific application and workload.
Are specs available?
--
vda