-- Jim
> On Feb 23, 2016, at 9:38 PM, David Burgess <[email protected]> wrote:
>
>> On Feb 23, 2016 7:01 PM, "Jim Thompson" <[email protected]> wrote:
>>
>> perhaps you have a different definition of ‘wire speed’. You have to
> fill the link with min-sized packets for “wire speed”.
>> (It’s trivial with large packets.)
>>
>> This is, of course, what is probably happing with 2-3K
>
> The definition I had in mind was 1000 megabits per second in both
> directions. I wasn't concerned with packet rates at that moment, and I
> can't tell you what numbers I was getting because I don't remember, and
> perhaps I didn't even record them.
Doesn't matter.
1Gbps of min-sized (64 byte, or 84 bytes including IFG (12 bytes of 'time'),
preamble, SFD & CRC) equates to 1,488,095 packets per second.
1Gbps of max-sized (1500 byte, or 1536 bytes including IFG (12 bytes of
'time'), preamble, SFD & CRC) equates to 81,380 packets per second.
Neither FreeBSD or Linux will forward packets at 1.488Mpps on any conceivable
commodity hardware.
netmap-fwd will do 1.2Mpps on a 1.7GHz C2000 (2220) and the type of minimal
routing table often found in pfSense installations.
Our DPDK router will do > 10Mpps with a full (570,000 routes) BGP route table,
and a rather large ACL table on a Broadwell-DE platform.
> I think we all agree that if the OP has a lot of gamers online then small
> packets and high packet rates are going to be a concern.
High packet rates are a much larger issue than raw bandwidth.
> Thanks for the info on the new technologies. Networking is not boring
> pursuit.
"Networking is the Vietnam of computing. Something can nuke you from behind,
and it's gone when you turn around. It's impossible to win a guerrilla war
against a highly distributed enemy." -- Mike Smith
I am Agent Orange.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
