process a syn flood if they have identical
hardware? Oh and btw the recieving side could only do 400k pps.
Thanks!
Alex
On 05/20/2013 11:45 PM, John R Pierce wrote:
> On 5/20/2013 10:24 PM, Alex Flex wrote:
>> We run a reverse proxy so our CPU need for that is very small, plus we
>>
Hello again John, I only have one network adapter. GigE.
Perhaps anybody else can give me another suggestion in order to achieve
this?
Thanks
Alex
On 05/20/2013 11:38 PM, John R Pierce wrote:
> On 5/20/2013 10:39 PM, Alex Flex wrote:
>> In summary, its very easy to hit a low number o
John,
On 05/20/2013 10:48 PM, John R Pierce wrote:
>
> afaik, IRQs from a single device have to be handled serially, you can't
> have more than one active IRQ at the same time.
>
> so there's really no point in distributing them across multiple CPU
> cores. let the other cores handle user space a
John,
We run a reverse proxy so our CPU need for that is very small, plus we
get syn flooded often.. which is why we have the need to be able to load
between cores, i think it is justified.
Thanks
Alex
On 05/20/2013 10:48 PM, John R Pierce wrote:
> On 5/20/2013 9:53 PM, Alex Flex wrote:
&
Hello again guys,
Iam trying to asses the best hardware for a machine that procceses a
high number of packets per second on its NIC. THe only way I can achieve
this without guesses is If iam able to understand or test what the
number of interrupts available per core and how to translate that to
Hello CentOS !
Iam trying to configure a Dual Core 1.6Ghz AMD E-350 machine to be able
NIC (eth0) interrupts the most efficient way possible so that I can be
able to handle the large number of random source packets per second.
Currently running CentOS 6.4 2.6.32-358.6.2.el6.x86_64, i made some
6 matches
Mail list logo
