ipng/ipng.ch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move shared iconography into a shared assets folder

Browse Source
This commit is contained in:
Pim van Pelt
2024-08-05 21:27:08 +02:00
parent 0542c1e2d9
commit 20022b77dd
26 changed files with 21 additions and 120 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/articles/2024-07-05-r86s.md
View File

@ -292,7 +292,7 @@ transmitting, or performing both receiving *and* transmitting.
### Intel X520 (10GbE)
{{< image width="100px" float="left" src="/assets/oem-switch/warning.png" alt="Warning" >}}
{{< image width="100px" float="left" src="/assets/shared/warning.png" alt="Warning" >}}
This network card is based on the classic Intel _Niantic_ chipset, also known as the 82599ES chip,
first released in 2009. It's super reliable, but there is one downside. It's a PCIe v2.0 device
@ -462,7 +462,7 @@ ip4-rewrite active 14845221 35913927 0 8.9
unix-epoll-input polling 22551 0 0 1.37e3 0.00
```
{{< image width="100px" float="left" src="/assets/vpp-babel/brain.png" alt="Brain" >}}
{{< image width="100px" float="left" src="/assets/shared/brain.png" alt="Brain" >}}
I kind of wonder why that is. Is the Mellanox Connect-X3 such a poor performer? Or does it not like
small packets? I've read online that Mellanox cards do some form of message compression on the PCI