server NUC5i3RYB (eth I218-V), NAT between them, <1 ms latency
(everything on the same table), IPv4 unless specified,
using iperf3 LAN=>WAN and -R for WAN=>LAN (both TCP).
With the TP-Link firmware:
- wired 930+ Mbit/s both ways
- wireless 5G 560+ Mbit/s down 440+ Mbit/s up
- wireless 2.
alternative to
>>>>> the classic forwarding path, that is faster. Packets kick in at the
>>>>> Netfilter ingress hook (right at the same location as 'tc' ingress),
>>>>> if there is a hit in the software flowtable, ttl gets decremented,
>>>&g
a hit in the software flowtable, ttl gets decremented,
>>>> NATs are done and the packet is placed in the destination NIC via
>>>> neigh_xmit() - through the neighbour layer.
>>>
>>> Hi Pablo,
>>>
>>> I tested today a few things on a brand ne
gt;WAN and -R for WAN=>LAN (both TCP).
>>
>> > With the TP-Link firmware:
>> > - wired 930+ Mbit/s both ways
>> > - wireless 5G 560+ Mbit/s down 440+ Mbit/s up
>> > - wireless 2.4G 100+ Mbit/s both ways
>>
gt;> the classic forwarding path, that is faster. Packets kick in at the
>>>>> Netfilter ingress hook (right at the same location as 'tc' ingress),
>>>>> if there is a hit in the software flowtable, ttl gets decremented,
>>>>> NATs are done and the
To make it more accessible for nodejs users to configure and run a build
on mips target lacking hardware fpu
Signed-off-by: Yousong Zhou
---
v2 <- v1
Use TARGET_lantiq_ase instead of TARGET_lantiq
config/Config-kernel.in| 5 +
hing on the same table), IPv4 unless specified,
> using iperf3 LAN=>WAN and -R for WAN=>LAN (both TCP).
>
> With the TP-Link firmware:
> - wired 930+ Mbit/s both ways
> - wireless 5G 560+ Mbit/s down 440+ Mbit/s up
> - wireless 2.4G 100+ Mbit/s both ways
>
> With OpenWRT/
To make it more accessible for nodejs users to configure and run a build
on mips target lacking hardware fpu
Signed-off-by: Yousong Zhou
---
config/Config-kernel.in| 5 +
target/linux/lantiq/ase/config-default | 1 -
target/linux/pistachio/config-4.9
Tested-by: Stijn Segers
Compile and run-tested on ar71xx / ramips/mt7621 / x86/64.
Op za, 27 jan 2018 om 5:05 , schreef Kevin Darbyshire-Bryant
:
Refresh patches.
Refresh x86/config for RETPOLINE.
More Meltdown & Spectre mitigation.
Can this bug be fixed?
2018-01-26 11:14 GMT+01:00 Ansuel Smith :
> Then the bug is real.
>
> Il 26 Gen 2018 08:01, "Nishant Sharma" ha scritto:
>>
>> Hi,
>>
>> On Friday 26 January 2018 04:18 AM, Ansuel Smith wrote:
>>>
>>>
10 matches
Mail list logo